QA/Sync/Test Plan/grinder tests: Difference between revisions

The objective of these scripts is to match our use of the sync api as closely as possible to that of the firefox client. The [https://wiki.mozilla.org/Services/Sync/Server/API/Storage/1.1 Sync API] is a fairly general storage solution - the behavior of the firefox client needs to be mimicked. A client object has been created as a mechanism to mimick the actions of a firefox client in grinder. The following functions are used to manipulate the test client to preform tasks a server normally recieves.

* Create User

* Add Data - these functions simulate a user creating data

** Tabs

*** Tabs are a whole different system - they aren't stored in memory

** Bookmarks

** History

** Preferences

** Passwords

* Sync - These functions simulate the client going to the sync server and performing the sync routine

** Standard Sync

** Mobile Sync (Takes data in chunks of 50, processes them, and then asks for more)

** Change sync key

 

New functions can be added as new services are rolled out. A lot of potential use cases will be able to be simulated by this system. For example a dupes test could be run by syncing the same data multiple times with serperate client objects.