[cvs] [Wiki] changed: SyncMLConformanceTestSuite

[Wiki Guest]

guest [85.181.55.187]  Sat, 29 Jul 2006 01:35:53 -0700

Modified page: http://wiki.horde.org/SyncMLConformanceTestSuite
New Revision:  1.2
Change log:  more test results

@@ -11,26 +11,26 @@
  ||0203|| ##green|passed##  || To check if the Test Object responds with Results for a Get on device information.||
  ||0204|| ##green|passed##  || To check if the Test Object responds with Alerts for all the databases                     alerted by SCTS.||
  ||0205|| ##green|passed## || To check if the Test Object sends valid Sync Tags.||
  ||0204|| ##green|passed## || To check if the Test Object responds with Alerts for multiple                     databases alerted by SCTS.||
-||0301|| || To check if the Test Object's and SCTS' Sync Anchors match by                     sending/receiving Alerts for normal two way sync.||
-||0302|| || To check if the Test Object handles Adds correctly.||
-||0401|| || To check if the Test Object sends valid Adds.||
-||0402|| || To check if the Test Object handles a Replace on a data item added by SCTS.||
-||0403|| || To check if the Test Object sends a valid Replace on a data item added                     by SCTS.||
-||0404|| || To check if the Test Object handles a Delete on a data item added by SCTS.||
-||0405|| || To check if the Test Object sends a valid Delete on a data item added                     by SCTS.||
-||0501|| || To check if the Test Object handles a Replace on a data item added by it.||
-||0502|| || To check if the Test Object sends a valid Replace on a data item added                     by it.||
-||0503|| || To check if the Test Object handles a Delete on a data item added by it.||
-||0504|| || To check if the Test Object sends a valid Delete on a data item added                     by it.||
-||0505|| || To check if the Test Object handles a Replace on a non-existant data                     item as an Add.||
-||0601|| || To check if the databases are in Sync by forcing a slow sync (SCTS                     does not send any modifications).||
-||0701|| || To check if the Test Object responds with an appropriate status code                     for a Delete with a nonexistent target/source.||
+||0301|| ##ref|crash## || To check if the Test Object's and SCTS' Sync Anchors match by                     sending/receiving Alerts for normal two way sync.||
+||0302|| ##ref|crash## || To check if the Test Object handles Adds correctly.||
+||0401|| ##green|passed## || To check if the Test Object sends valid Adds.||
+||0402|| ##ref|crash## || To check if the Test Object handles a Replace on a data item added by SCTS.||
+||0403|| ##ref|crash## || To check if the Test Object sends a valid Replace on a data item added                     by SCTS.||
+||0404|| ##ref|crash## || To check if the Test Object handles a Delete on a data item added by SCTS.||
+||0405|| ##ref|crash## || To check if the Test Object sends a valid Delete on a data item added                     by SCTS.||
+||0501|| ##ref|crash## || To check if the Test Object handles a Replace on a data item added by it.||
+||0502|| ##ref|loop## || To check if the Test Object sends a valid Replace on a data item added                     by it.||
+||0503|| ##ref|crash##|| To check if the Test Object handles a Delete on a data item added by it.||
+||0504|| ##ref|crash## || To check if the Test Object sends a valid Delete on a data item added                     by it.||
+||0505|| ##ref|crash##  || To check if the Test Object handles a Replace on a non-existant data                     item as an Add.||
+||0601|| ##ref|crash##  || To check if the databases are in Sync by forcing a slow sync (SCTS                     does not send any modifications).||
+||0701|| ##ref|crash##  || To check if the Test Object responds with an appropriate status code                     for a Delete with a nonexistent target/source.||
  ||0801|| ##green|passed## || To check if the Test Object handles sync without seperate intialization.||
-||0901|| || To check if the Test Object can handle an Add with multiple items.||
-||0902|| || To check if the Test Object can handle a Replace with multiple items.||
-||0903|| || To check if the Test Object can handle a Delete with multiple items.||
+||0901|| ##ref|crash## || To check if the Test Object can handle an Add with multiple items.||
+||0902|| ##ref|crash## || To check if the Test Object can handle a Replace with multiple items.||
+||0903|| ##ref|crash## || To check if the Test Object can handle a Delete with multiple items.||
  ||0904|| || To check if the Test Object responds with individual 'Status' for each                     item in a Replace (One item is non-existant).||
  ||0905|| || To check if the Test Object responds with individual 'Status' for each                     item in a Delete (One item is non-existant).||
  ||1001|| || To check if the Test Object can handle multiple messages.||
  ||1101|| || To check if the Test Object determines from the !DevInfo whether or not                     !NumberOfChanges is supported, and if it sends proper !NumberOfChanges information                     to SCTS.||
@@ -74,5 +74,9 @@
  ||2321|| || To check the Test Object ability to handle filtering with                     "luid-expression = "LUID;" log-equalitycomp string-value" filter grammar type.||
  ||2322|| || To check the Test Object ability to handle filtering with "ct-no-value                     = "NULL;"; No property value for the item" filter grammar type.||
  ||2323|| || To check the Test Object ability to handle filtering with                     "ct-filter-keyword = string-value; Valid content-type specific filter keywords"                     filter grammar type.||
  ||2324|| || To check the Test Object ability to handle filtering with                     "ct-filter-value = string-value ; Valid content-type specific property value"                     filter grammar type.||
+
+//Note:// ##red|Crash## means the Testing Suite crashed, not the horde Server... ##red|Loop## means the test suite indefinetly sends identical messages.
+
+After an incomplete test you may have to manually remove the session data from your php session directory. Otherwise a session may get reused in the next text: this results in a failed test as the server does not request authoriasation again.