The presentation shows how an automated test for native SyncML clients works and how to develop it. You'll learn how to get the logs from the devices, assembly the test, run it and check that Funambol server and synclets do not break between a release and another, or after committing a piece of code. Watch this presentation if you want to improve the automated tests for SyncML devices

1. Developement of Automated Tests for native SyncML clients January 27 th , 2009 Andrea Scova

3. Building an Automated Test for native SyncML clients

4. Automated Tests Maintenance

5. Conclusions

6. Questions & Answers

8. after a commit of a single piece of code

9. (e.g. a fix for a synclet) Introduction

12. costs (devices, QA time)

13. simulation of native SyncML client based on server's log

15. compare expected behaviour of the server against its actual behaviour simulated environment Building an Automated Test for native SyncML clients =

17. the server sends back the same items to the client (after updating the status)

18. NOTE: one syncsource per time

20. catch the full logs

21. create the items (single syncsource) on the real device

22. all available fields on the device should be filled

23. include symbols and language specific chars (e.g. &, @, $, %, â, ã, ä, å, è, é)

24. SYNC

26. create single .xml files

27. create header.properties

28. from HTTP header (e.g. user-agent: Nokia SyncML HTTP Client)

30. server-URI -> http://localhost:8080/funambol/ds

31. sessionID

32. Building an Automated Test for native SyncML clients Editing the SyncML messages

34. Directory structure naming convention needed to make Automated Tests work [ Manufacturer ]/ [ Model_Syncsource ]/ error / reference / response / Building an Automated Test for native SyncML clients

36. add/modification/deletion of a property (e.g. add a new field in the contacts) If NOT maintained the Automated Tests will systematically fail

38. for every device 3/4 syncsources to be automatized

39. maintenance

40. Questions & Answers ...