diff options
Diffstat (limited to 'HACKING')
| -rw-r--r-- | HACKING | 11 |
1 files changed, 7 insertions, 4 deletions
@@ -139,7 +139,10 @@ then run "src/client-test" as described in src/client-test-app.cpp. It understands several environment variables, among them: - CLIENT_TEST_SERVER = chooses config - CLIENT_TEST_SOURCES = comma separated list of enabled sources, identified - by their name (ical20, vcard21, vcard30, itodo20, text (= memos)) + by their name + For Evolution: eds_contact,eds_event,eds_task,eds_memo + For file backend: file_contact,file_event,file_task,file_memo (uses same test + data and vCard flavor as Evolution) - CLIENT_TEST_EVOLUTION_PREFIX=[name|file://<path>] overrides the evolutionsource setting in the configuration; if file:// is used then these database will be created automatically @@ -361,7 +364,7 @@ SyncEvolution enables Buteo testing based client-test. Configure with "src/client-test" to test Buteo with the above described environment variables. The only difference is that you have to set a new one "CLIENT_TEST_BUTEO=1". Buteo testing supports testing two kinds of -data: qt_vcard30 and kcal_ical20. +data: qt_contact and kcal_event. Here are step-by-step instructions to get started with Buteo testing, also using ScheduleWorld as example: @@ -377,5 +380,5 @@ also using ScheduleWorld as example: => change the access mode of the directory /etc/sync - CLIENT_TEST_SERVER=scheduleworld \ CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/testing/ \ - ./client-test Client::Sync::qt_vcard30 - => runs all tests for qt_vcard30 + ./client-test Client::Sync::qt_contact + => runs all tests for qt_contact |