B2G/QA/Gaia Test Plan: Difference between revisions
Jump to navigation
Jump to search
| Line 52: | Line 52: | ||
* Communicate with project leads | * Communicate with project leads | ||
* Know the tracking bugs -- nudging with necessary | * Know the tracking bugs -- nudging with necessary | ||
== Additional References == | == Additional References == | ||
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email_Templates Email Templates] | * [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email_Templates Email Templates] | ||
Revision as of 20:10, 3 September 2012
Test Plan
Summary
| Lead | John Hammink (irc: jammink) |
| Contributors |
|
| Status | Pre-release, approaching Milestone 4 |
| Tracker | Feature Dashboard |
| Project Page | B2G/QA |
| References | Instructions for Contributors |
Scope
Strategy
Currently only directed exploratory testing is being performed. There is also a daily suite of smoke tests run against trunk (ie. can a phone call be made, etc). As the platform and supported applications harden the strategy will shift to: a suite of tests (manual & automated) that balance risk with speed of reporting, performance, and security.
Current focus areas and needs
- writing test plans based off of the specifications we have for features
- writing test cases and adding them to the feature test logs
- testing particular areas and filing bugs
- verify that featured apps match their spec
- verifying and closing bugs with features & defects that have landed
Environments
- Using a desktop build or an Otoro phone (tier 1 environments)
- Using a Samsung Galaxy S2 or Galaxy Nexus (tier 2 environments)
Steward Responsibilities
- Writing exploratory test cases
- Running test cases
- Ensuring the app meets it’s spec
- Knowing the apps current status & progress
- Communicate with project leads
- Know the tracking bugs -- nudging with necessary