19f5d50e61
Monotone-Revision: 65d93d27a238a5e86f0c7bc9fd3cbc658d5ee681 Monotone-Author: wsourdeau@inverse.ca Monotone-Date: 2009-08-06T21:41:19 Monotone-Branch: ca.inverse.sogo
56 lines
1.9 KiB
Plaintext
56 lines
1.9 KiB
Plaintext
setup
|
|
-----
|
|
|
|
(you need "python-xml" and "python-m2crypto" in order to run the scripts)
|
|
|
|
1) copy testconfig.py.in to testconfig.py (make sure to never EVER add it to monotone)
|
|
2) edit testconfig.py to suit your environment
|
|
3) run the test scripts
|
|
|
|
runnable scripts
|
|
----------------
|
|
|
|
all.py - run all scripts below at once
|
|
webdavsync.py
|
|
davacl.py
|
|
|
|
other scripts
|
|
-------------
|
|
|
|
propfind.py - a sample implementation of a PROPFIND request using webdavlib
|
|
|
|
* developers
|
|
------------
|
|
|
|
- Test methods are always prefixed with "test". Sometimes, it's easier to
|
|
track down a problem by enabling only one test at a time. One possible method
|
|
is to replace "def test" with "def xtest" and replace it back when the
|
|
problems are solved.
|
|
|
|
- Test failures start with "FAIL:". Those are the ones that indicate possible
|
|
bugs in the application, if the test is well written.
|
|
For example like this:
|
|
|
|
======================================================================
|
|
FAIL: 'modify' PUBLIC, 'view all' PRIVATE, 'view d&t' confidential
|
|
----------------------------------------------------------------------
|
|
Traceback (most recent call last):
|
|
File "./davacl.py", line 75, in testModifyPublicViewAllPrivateViewDConfidential
|
|
self._testRights({ "pu": "m", "pr": "v", "co": "d" })
|
|
File "./davacl.py", line 119, in _testRights
|
|
self._testCreate(rights)
|
|
File "./davacl.py", line 165, in _testCreate
|
|
exp_code)
|
|
File "./davacl.py", line 107, in _putEvent
|
|
% (exp_status, put.response["status"]))
|
|
AssertionError: event creation/modification: expected status code '403' (received '201')
|
|
|
|
- Test errors start with "ERRORS" and most likely indicate a bug in the test
|
|
code itself.
|
|
|
|
- Always set a doc string on the test methods, especially for complex test
|
|
cases
|
|
|
|
- When writing tests, be aware that contrary to unit tests, functional tests
|
|
often imply a logical order between the different steps
|