[cvs] [Wiki] changed: SyncMLCreateTestCases

[Karsten Fourmont]

karsten  Sun, 26 Aug 2007 08:14:22 -0700

Modified page: http://wiki.horde.org/SyncMLCreateTestCases
New Revision:  1.9
Change log:  removed outdated note

@@ -1,7 +1,5 @@
 + How to write a !SyncML test case
-
-##red|Note (January, 13th): There is an upcoming new release of the SyncML
package. It includes some final changes to protocol implementation. So
please wait for this release before actually creating test cases. Thank
you.##

 The !SyncML package contains a testing script to replay prerecorded test
sessions. This allows the developers to check if changes break things for
one particular phone. So it would be great to have test cases for as many
phones as possible.

 Each test case should be for one database (like calendar or addressbook,
but not both). The exception is for phones that handle tasks and calendar in
one database like the P900 does. Here you should create test entries for
tasks and calendar at the same time to see if it works properly.
@@ -9,9 +7,9 @@
 Here's how to create a test case:

 * Preparations in Horde:
  * create a user "syncmltest" with password "syncmltest" in horde. If the
user's already there first delete and then recreate to get a fresh start.
- * create at least one test entry in the app you want to test
(kronolith|nag|mnemo|turba). The entry should be named like "server##" (e.g.
server1) and the description should contain an umlaut for charset testing.
If you're creating a test case for the calendar, you should create at least
two: one with an all day event and one with a normal (like 2hour) event.
+ * create at least one test entry in the app you want to test
(kronolith|nag|mnemo|turba). The entry should be named like "server##" (e.g.
server1) and the description should contain an umlaut for charset testing.
If you're creating a test case for the calendar, you should create at least
two: one with an all day event and one with a normal (like 2hour) event.
Generally the entries should make use of as many features (alarms, due
dates, ...) as possible.

 * Preparations in the Client (PDA/Outlook/whatever)
  * Create at least one test entry named "client##". The database must only
contain this single entry (so you might need to do a backup of your phone
first). Other than that the same information as for the test entries in
horde above apply (umlauts, all day events).