https://sourceforge.net/p/coils/wiki/CalDAV%2520Tester/Recent changes to CalDAV TesterenThu, 05 Sep 2013 12:30:56 -0000https://sourceforge.net/p/coils/wiki/CalDAV%2520Tester/<div class="markdown_content"><pre>--- v3 +++ v4 @@ -1,4 +1,4 @@ -[Clients] [Development] +[Clients] [Development] [CalDAV] [WebDAV] #CalDAV Tester </pre> </div>Adam Tauno WilliamsThu, 05 Sep 2013 12:30:56 -0000https://sourceforge.net9d6f6d27a1b33f47bffeecba906ab8f048448d42https://sourceforge.net/p/coils/wiki/CalDAV%2520Tester/<div class="markdown_content"><pre>--- v2 +++ v3 @@ -1,4 +1,4 @@ -[Clients] +[Clients] [Development] #CalDAV Tester </pre> </div>Adam Tauno WilliamsThu, 05 Sep 2013 12:29:27 -0000https://sourceforge.net7869d0cb1749033b213354c73bec950ecc967f81https://sourceforge.net/p/coils/wiki/CalDAV%2520Tester/<div class="markdown_content"><pre>--- v1 +++ v2 @@ -4,3 +4,34 @@ - [CalDAV Tester Home Page](https://trac.calendarserver.org/wiki/CalDAVTester) +Most of the below was originally cut-n-pasted from the CalDAV Tester home page. + +##Configuring CalDAVTester + +As provided, CalDAVTester is already setup to operate with a Calendar Server running on the localhost using the caldavd-test.plist configuration. No changes are needed to the configuration files to run. + +CalDAVTester uses XML files for its configuration and tests, and a series of data files for data sent to the server. + + - The "serverinfo" configuration is stored in scripts/servers. That file defines details about the server being tested (its host name, port etc) as well as information about how the server is setup with user accounts for testing. CalDAVTester requires a certain number of user accounts to be present on the server being tested in order to perform the requird tests. The "serverinfo" configuration file allows you to specify the details for each account, including user name, password, path to calendars etc. These values are substituted into the tests via a string subtitution. The values can also be substituted into the data files as needed. + - The "caldavtest" test files are stored in scripts/tests. There are multiple test scripts each of which defines a set of tests to be executed against the server. Each test has a section where any required setup can be done (e.g. storing resources on the server needed for the test), and an section where clean-up can occur (e.g., removal of resources added during ). Multiple can be specified. Each suite can contain multiple . Each test can include one or more 's. A request carries out an HTTP transaction with the server and optionally verifies the result. + +##Running CalDAVTester + +First make sure your CalDAV server is up and running, then do the following: + +cd into the CalendarServer directory + + ./testserver + +This will run all CalDAV and CardDAV tests. + +If you want explicit control of what tests are run, do the following: + +cd into the CalDAVTester directory + + export PYTHONPATH=`./run.py -p` + ./testcaldav.py </pre><pre> + +where </pre><pre> is one of the .xml files in the CalDAVTester/scripts/test directory. For example, to run the 'well-known.xml' test for CalDAV, you would execute: + + ./testcaldav.py CalDAV/well-known.xml </pre> </div>Adam Tauno WilliamsThu, 05 Sep 2013 12:27:40 -0000https://sourceforge.netfab72f6246824ddc8f1ed7723613ab7323ab242fhttps://sourceforge.net/p/coils/wiki/CalDAV%2520Tester/<div class="markdown_content"><p><a class="alink" href="/p/coils/wiki/Clients/">[Clients]</a></p> <h1 id="caldav-tester">CalDAV Tester</h1> <ul> <li><a class="" href="https://trac.calendarserver.org/wiki/CalDAVTester" rel="nofollow">CalDAV Tester Home Page</a></li> </ul></div>Adam Tauno WilliamsThu, 05 Sep 2013 12:22:46 -0000https://sourceforge.net1bae4269fb6b71b6da21a088a4381f446591ff25