Tik-76.115 System Test Report

SyncML

Document Information

Document name	system_test_report-20010315.html
Author	JI
Last updated	$Id: system_test_report-20010315.html,v 1.2 2001/03/19 22:05:49 jaikonen Exp $

Document Revisions

Version	Date	Updater	Description
0.1	19.3.2001	JI	Document created

1. Test Situation

Date:	15.3.2001
Time:	20.00-23.00
Location:	Smartner, Helsinki
Participants:	AS, ER, SH, JI
Notes:	Most of the system tests were already designed. Since majority of the test cases had been passed without problems yesterday, everything was expected to go smoothly. The quality responsible was present to verify that the testers understood how the test cases were meant to be performed.

2. Test Results

Test suite	Notes	Status
test.TwoWaySyncSystemTest	The testClientModify test case was failed. After an entry in the server was modified, the next synhronization returned the original contents of the entry from the client. This problem was not visible during the previous system testing session because of a misunderstanding about how the test case should be performed. Modifying the name field is similar to deleting an entry and adding the entry with a different name, so a different kind of synchronization is performed in that case.	failure
test.ConflictResolverSystemTest	It is not possible to change the conflict resolver in the server since the constructor of the SmartResolver takes wrong arguments. SmartResolver should be split in several separate classes, one for each conflict resolver type. We decided to abort testing since the problems found made it impossible to perform most test cases meaningfully.	failure

Test suite

Notes

Status

test.TwoWaySyncSystemTest

The testClientModify test case was failed. After an entry in the server was modified, the next synhronization returned the original contents of the entry from the client. This problem was not visible during the previous system testing session because of a misunderstanding about how the test case should be performed. Modifying the name field is similar to deleting an entry and adding the entry with a different name, so a different kind of synchronization is performed in that case.

failure

test.ConflictResolverSystemTest

It is not possible to change the conflict resolver in the server since the constructor of the SmartResolver takes wrong arguments. SmartResolver should be split in several separate classes, one for each conflict resolver type.

We decided to abort testing since the problems found made it impossible to perform most test cases meaningfully.

failure

3. Conclusions

Test status:	failure
Approved by:	N/A
Notes:	The problems have to be fixed as soon as possible. Test suites for replication need to be implemented. Test cases that involve modifications need to be rephrased to make sure that the name field is not modified.