[cvs] [Wiki] changed: SyncMLConformanceTestSuite

[Karsten Fourmont]

karsten  Sun, 29 Oct 2006 04:59:04 -0800

Modified page: http://wiki.horde.org/SyncMLConformanceTestSuite
New Revision:  2.0
Change log:  We now pass all tests!

@@ -23,25 +23,25 @@
  ||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|| ##green|passed## || 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).||
+||0601|| ##green|passed## || To check if the databases are in Sync by forcing a slow sync (SCTS                     does not send any modifications). **Note: You have to start this test with an empty databse.**||
  ||0701|| ##green|passed## || 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. ** Note: In this test the suite doesn't send Map commands to the server. Thus horde keeps the session open. Before proceeding to the next test you have to clean the session data (like /var/lib/php(5)) so horde requests a new authorisation for test 0901. Othewise test following tests will fail. **||
  ||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|| ##green|passed## || To check if the Test Object responds with individual 'Status' for each                     item in a Replace (One item is non-existant).||
  ||0905|| ##green|passed## || 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.||
+||1101|| ##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.||
  ||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.||
+||1301||  ##green|passed##  || 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||  ##gren|passed## || To check if the Test Object determines from the !DevInfo whether or not                     Large Objects are supported.||
+||1501||  ##green|passed##  || 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||  ##green|passed## || To check if the Test Object correctly handles Large Objects with                     incorrect size.||
+||1602||  ##green|passed##  || To check if the Test Object correctly handles large objects that are                     not completely sent.||
+||1701||  ##green|passed## || 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