QA/Test Pilot Test Plan: Difference between revisions

QA/Test Pilot Test Plan (view source)

710 bytes removed , 5 April 2010

m

Confirmed users

4,072

edits

@@ Line 20: / Line 20: @@
 * Areas of test coverage
 ** Installing/Upgrading the extension
-** ''It is very important to ensure the quality for the following experiences, since it represents the ability for Test Pilot to roll out studies and gain data. This process won't be changed by individual studies.'' Verify:
+** Extension UI points
-**# if users are able to quit the study after they opt in
+*** Menu Items
-**# if users are able to submit data when the study finishes
+*** Notifications
-**# if the data is still being collected when the study finishes
+** Verify interfaces for surveys, experiments, etc.
-**# if data set is empty
+*** studies are present, active and submittable (when appropriate)
-**# if users are asked again to submit their data after the submission
+*** multiple active studies.
-**# if the study is associated well with the survey
-**# if users are able to participate multiple studies at the same time
-**# if users get notification during the correct time
-**The log and instruments for each concrete study.  ''This is very crucial for Test Pilot to get correct and meaningful data. For Q2, one study is scheduled per month.''
 ** Access to various pages linked from the extension or survey
-** Verify interfaces for surveys, experiments, etc.
-* Attempt to verify bug fixes a couple times a month
+* Verify bug fixes a couple times a month
 * Unit tests from developers?