QA/Test Pilot Test Plan: Difference between revisions
< QA
Jump to navigation
Jump to search
m (→Test Strategy) |
|||
Line 21: | Line 21: | ||
*** Menu Items | *** Menu Items | ||
*** Notifications | *** Notifications | ||
** Verify interfaces for | ** Verify interfaces for study access. | ||
*** studies are present, active and submittable (when appropriate) | *** studies are present, active and submittable (when appropriate) | ||
*** multiple active studies. | *** multiple active studies. |
Revision as of 17:47, 9 April 2010
- Test Pilot Test Plan
Overview
Test Pilot is a platform aimed at collecting structured user feedback and log data from Firefox and other Mozilla Labs experiments.
Mozilla Labs - Test Pilot Project Page
Test Pilot Home Page
Test Pilot Blog
Labs Weekly Planner
Builds
Test Strategy
Mozilla QA will be taking a lightweight testing approach to Test Pilot.
- Areas of test coverage
- Installing/Upgrading the extension
- Extension UI points
- Menu Items
- Notifications
- Verify interfaces for study access.
- studies are present, active and submittable (when appropriate)
- multiple active studies.
- Access to various pages linked from the extension or survey
- Verify bug fixes a couple times a month
- Unit tests from developers?
- Areas not tested
- data integrity/correctness on server end
- long term regular interaction with Test Pilot tests (this is better left for our community)
- Browser Versions covered
- Firefox 3.6 (primary)
- Firefox next (spot check if time allows)
- Operating systems covered
- Windows
- 7 (primary)
- XP (spot check if time allows)
- Apple
- Snow Leopard (10.6) (primary)
- Linux (spot check if time allows)
- Windows
Schedule Scoping
- We would like QA to give each new version of the Test Pilot Extension itself as well a each new test a quick once over before it is released as a sanity check. We'll be flexible in doing this smoke testing any time in the development cycle for that release.
Bugs
Contacts
- Developer - Jono
- QA - Tracy