Confirmed users
1,905
edits
Auto-tools/Projects/CrossWeave/Test Format: Difference between revisions
Auto-tools/Projects/CrossWeave/Test Format (view source)
Revision as of 17:57, 20 May 2010
, 20 May 2010→Phase Actions
| Line 92: | Line 92: | ||
*** "wipe-server": true, causes all data on the Weave server to be wiped before the sync takes place | *** "wipe-server": true, causes all data on the Weave server to be wiped before the sync takes place | ||
* '''add''': populates the browser with the given assets | * '''add''': populates the browser with the given assets | ||
* '''verify''': verifies that the given assets exist in the browser | * '''verify''': verifies that the given assets exist in the browser | ||
* '''verify-not''': verifies that the given assets do not exist in the browser | * '''verify-not''': verifies that the given assets do not exist in the browser | ||
For all actions other than '''sync''', the action's value is an object with one or more key-value pairs denoting valid asset lists. Each key in this object is one of: | |||
* '''bookmarks''' | |||
* '''passwords''' | |||
* '''history''' | |||
* '''tabs''' (not yet implemented) | |||
* '''formdata''' (not yet implemented) | |||
* '''prefs''' (not yet implemented) | |||
and each key's value is the name of the relevant asset list in the test file. | |||
== Putting It All Together == | == Putting It All Together == | ||