1,285
edits
Weave Load Test Plan/WeaveLiveUserLoadTestPlan: Difference between revisions
Jump to navigation
Jump to search
Weave Load Test Plan/WeaveLiveUserLoadTestPlan (view source)
Revision as of 06:59, 5 May 2010
, 5 May 2010→Tests to Perform
| Line 31: | Line 31: | ||
= Tests to Perform = | = Tests to Perform = | ||
== [1] Functionality Smoke Tests == | |||
;Phase 1 | |||
As mentioned above, the load test will be done in 2 phases. The first phase is to install firefox and create the user data followed by <u>[1] Functionality Smoke Tests</u> and then <u>[2] Sync Performance Tests</u>. After the first phase, user should save their user profile data. | |||
;Phase 2 | |||
The second phase will be conducted several days later when the weave systems is at the full load capacity. In the second phase the tests will be conducted in reverse order <u>[2] Sync Performance Tests</u> and the <u>[1] Functionality Smoke Tests</u>. Phase 2 should begin with the reload of the saved profile data. | |||
==== [1] Functionality Smoke Tests ==== | |||
* With both systems weave data synchronized, ensure user data update operations are reflected in the secondary browser instance after a weave sync: | * With both systems weave data synchronized, ensure user data update operations are reflected in the secondary browser instance after a weave sync: | ||
| Line 39: | Line 48: | ||
** data merge (bookmark tags) | ** data merge (bookmark tags) | ||
== [2] Sync Performance Tests == | ==== [2] Sync Performance Tests ==== | ||
* <u><b>weave delete local and download weave server data synchronization performance test</b></u> | * <u><b>weave delete local and download weave server data synchronization performance test</b></u> | ||
*# clear activity log | *# clear activity log | ||