[cvs] [Wiki] changed: SyncMLConformanceTestSuite

[Karsten Fourmont]

karsten  Sun, 30 Jul 2006 03:20:48 -0700

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

@@ -17,31 +17,31 @@
  ||0401|| ##green|passed##  || To check if the Test Object sends valid Adds.||
  ||0402|| ##green|passed##  || To check if the Test Object handles a Replace on a data item added by SCTS.||
  ||0403|| ##green|passed##  || To check if the Test Object sends a valid Replace on a data item added                     by SCTS.||
  ||0404|| ##green|passed##  || To check if the Test Object handles a Delete on a data item added by SCTS.||
-||0405|| ##ref|failed## || 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.||
-||0801|| || 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.||
-||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.||
-||1201|| || 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.||
-||1301|| || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported, and if it properly declares the !MaxObjSize and can                     properly receive Large Objects.||
-||1401|| || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported.||
-||1501|| || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported, and if it properly declares the !MaxObjSize and can                     properly send Large Objects.||
-||1601|| || To check if the Test Object correctly handles Large Objects with                     incorrect size.||
-||1602|| || To check if the Test Object correctly handles large objects that are                     not completely sent.||
-||1701|| || To check if the Test Object did not commit the Large Object with                     incorrect size and the incomplete Large Object sent in the last session.||
+||0405|| ##red|failed## || To check if the Test Object sends a valid Delete on a data item added                     by SCTS.||
+||0501|| ##green|passed## || To check if the Test Object handles a Replace on a data item added by it.||
+||0502|| ##green|passed## || To check if the Test Object sends a valid Replace on a data item added                     by it.||
+||0503|| ##green|passed## || To check if the Test Object handles a Delete on a data item added by it.||
+||0504|| ##green|passed## || To check if the Test Object sends a valid Delete on a data item added                     by it.||
+||0505|| ##red|failed## || To check if the Test Object handles a Replace on a non-existant data                     item as an Add.||
+||0601|| ##green|passed## || To check if the databases are in Sync by forcing a slow sync (SCTS                     does not send any modifications).||
+||0701|| ##red|failed## || 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|| ##green|passed## || To check if the Test Object can handle an Add with multiple items.||
+||0902|| ##green|passed## || To check if the Test Object can handle a Replace with multiple items.||
+||0903|| ##green|passed## || To check if the Test Object can handle a Delete with multiple items.||
+||0904|| ##red|failed## || To check if the Test Object responds with individual 'Status' for each                     item in a Replace (One item is non-existant).||
+||0905|| ##red|failed## || To check if the Test Object responds with individual 'Status' for each                     item in a Delete (One item is non-existant).||
+||1001|| ##green|passed## || To check if the Test Object can handle multiple messages.||
+||1101|| ##red|failed## || 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.||
+||1201|| ##green|passed## || 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.||
+||1301||  ##red|failed##  || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported, and if it properly declares the !MaxObjSize and can                     properly receive Large Objects.||
+||1401||  ##red|failed## || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported.||
+||1501||  ##red|failed##  || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported, and if it properly declares the !MaxObjSize and can                     properly send Large Objects.||
+||1601||  ##red|failed## || To check if the Test Object correctly handles Large Objects with                     incorrect size.||
+||1602||  ##red|failed##  || To check if the Test Object correctly handles large objects that are                     not completely sent.||
+||1701||  ##red|failed## || To check if the Test Object did not commit the Large Object with                     incorrect size and the incomplete Large Object sent in the last session.||
  
  
  
  ++ Test Results for !SyncML V1.2 Server Tests