Confirmed users
4,072
edits
m (→Test Strategy) |
|||
(5 intermediate revisions by 2 users not shown) | |||
Line 19: | Line 19: | ||
#Weave Client Extension Testing (Lead: Tracy Walker) | #Weave Client Extension Testing (Lead: Tracy Walker) | ||
#*This involves black box execution directly on the extension, testing the features and usage of the operation of the client. Involves data syncing and cross browsers and OS platform support. Will heavily include Fennec integration.<br> | #*This involves black box execution directly on the extension, testing the features and usage of the operation of the client. Involves data syncing and cross browsers and OS platform support. Will heavily include Fennec integration.<br> | ||
#Weave Client Load Testing (Lead: Matt Evans) | #Weave Client Load Testing (Lead: Matt Evans) | ||
#*This involves a collective approach to organizing weave users around the globe to create a load generation through the client to generate network traffic to production servers. | #*This involves a collective approach to organizing weave users around the globe to create a load generation through the client to generate network traffic to production servers. Still need to define measuring performance evaluation and instrumentation on what a successful network load would be. Likely outsourced.<br> | ||
#Weave Thick Client Server Testing (Lead: Jonathan Griffin) | #Weave Thick Client Server Testing (Lead: Jonathan Griffin) | ||
#*Data Driven Testing | #*Data Driven Testing | ||
#*Parametrize user credentials (so that it can be cloned out to X vms for cloud testing) | #*Parametrize user credentials (so that it can be cloned out to X vms for cloud testing) | ||
#*Use multiple profiles on the same machine (so that it can be easily cloned for testing and can be easily setup and run by hand by developers). <br> | #*Use multiple profiles on the same machine (so that it can be easily cloned for testing and can be easily setup and run by hand by developers). <br> | ||
== | == Areas Covered == | ||
#UI/front end - [http://spreadsheets.google.com/ccc?key=0AkSa2kZ0OBffdFMtR1NwZ2Nra29xMllTSlY2OExCUVE&hl=en Test case spreadsheet] | #UI/front end - [http://spreadsheets.google.com/ccc?key=0AkSa2kZ0OBffdFMtR1NwZ2Nra29xMllTSlY2OExCUVE&hl=en Test case spreadsheet] | ||
Line 44: | Line 44: | ||
#*Backward compatibility - 1.2b3 should be compatible to 1.2b2 | #*Backward compatibility - 1.2b3 should be compatible to 1.2b2 | ||
#*cross platform/product sync | #*cross platform/product sync | ||
#* see <'''Tracy's testplan (link here)'''> for more | |||
#Client Side Load Generation | |||
#* See <'''Matt's Testplan (link here)'''> for more | |||
#Thick Client load testing | |||
#* See <'''Jgriffin's Testplan (link here)'''> for more | |||
== Areas not covered == | |||
#Server/back end | #Server/back end | ||
#*[http://hg.mozilla.org/labs/weaveserver/file/1f3a04c1db3c/tests/load_data.pl Weave server test script] - run on changes and prior to pushes to stage. | #*[http://hg.mozilla.org/labs/weaveserver/file/1f3a04c1db3c/tests/load_data.pl Weave server test script] - run on changes and prior to pushes to stage. | ||
#Unit Test | #*Current implementation of server side tests include unit tests against the sync API. There are plans for Weave 1.3 to include the following: | ||
#**Registration API unit tests | |||
#**Load Balancing tests | |||
#**Failover/recovery tests? | |||
#**others... See Mike hanson and Tobi Elliot | |||
#Unit Test Frameworks | |||
#*Weave 1.3 will include a unit test framework hooked into tinderbox that includes nightly runs of tests. This will be handled by development. | |||
== Platform and product coverage == | == Platform and product coverage == | ||
Line 73: | Line 89: | ||
= Schedule Scoping = | = Schedule Scoping = | ||
*1. | *1.2 (released 4/9/2010) [https://wiki.mozilla.org/QA/Weave_Test_Plan/1.2 1.2 Client test plan] | ||
*1.3 (target 5/17) [https://wiki.mozilla.org/QA/Weave_Test_Plan/1.3 1.3 Client test plan] | |||
*1.3 (target 5/17) | |||
= Bugs = | = Bugs = |