38a2dbe3d2
Memotoo supports PERCENT-COMPLETE now. However, it sets the value to 100% if the status is completed. Therefore we can't have the 99% complete value in the eds_task test, as for other servers. |
||
---|---|---|
.. | ||
lcs | ||
templates/clients | ||
eds_contact.vcf | ||
eds_contact.vcf.apple.tem.patch | ||
eds_contact.vcf.exchange.tem.patch | ||
eds_contact.vcf.google.tem.patch | ||
eds_contact.vcf.memotoo.tem.patch | ||
eds_contact.vcf.mobical.tem.patch | ||
eds_contact.vcf.oracle.tem.patch | ||
eds_contact.vcf.Ovi.tem.patch | ||
eds_contact.vcf.syncevolution.tem.patch | ||
eds_contact.vcf.synthesis.tem.patch | ||
eds_contact.vcf.yahoo.tem.patch | ||
eds_contact.vcf.zyb.tem.patch | ||
eds_event-alarms-2010-12-31.ics | ||
eds_event.ics | ||
eds_event.ics.apple.tem.patch | ||
eds_event.ics.exchange.tem.patch | ||
eds_event.ics.funambol.tem.patch | ||
eds_event.ics.googlecalendar.tem.patch | ||
eds_event.ics.local | ||
eds_event.ics.memotoo.tem.patch | ||
eds_event.ics.mobical.tem.patch | ||
eds_event.ics.nokia_7210c.tem.patch | ||
eds_event.ics.oracle.tem.patch | ||
eds_event.ics.Ovi.tem.patch | ||
eds_memo.ics | ||
eds_memo.ics.memotoo.tem.patch | ||
eds_task.ics | ||
eds_task.ics.funambol.tem.patch | ||
eds_task.ics.memotoo.tem.patch | ||
eds_task.ics.mobical.tem.patch | ||
eds_task.ics.nokia_7210c.tem.patch | ||
eds_task.ics.Ovi.tem.patch | ||
google_event.ics | ||
local.png | ||
qt_contact.vcf | ||
README | ||
vcal10.ics | ||
vcard21.vcf | ||
yahoo_contact.vcf |
The test case files are as follows (take eds_task.ics as example): eds_task.ics (common case for all servers syncing with Evolution Data Server) eds_task.ics.funambol.tem (server specific case) During test, it will first try the server specific case(*.$server.tem), if not found fall back to the common case. To avoid redundancy, the server specific case is stored as a diff(patch) based on server common case. Makefile rules in src/Makefile-gen.am copy resp. create the necessary test files there every time the client-test program is built. Here's how this is used. To create new server specific test cases (using same example as above): - cd src - cp testcases/eds_task.ics testcases/eds_task.ics.funambol.tem - run client-test, edit, repeat... - commit modified patch files to git repo To update server specific test cases: - cd src - make client-test - edit testcases/eds_task.ics.funambol.tem - run client-test, edit, repeat... - commit modified patch files to git repo