B2G/QA/Gaia Test Plan: Difference between revisions
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
{| class="fullwidth-table" | {| class="fullwidth-table" | ||
|- | |- | ||
| style="width:20%" | '''Lead''' | | style="width:20%" | '''Gaia Lead''' | ||
| [mailto:jhammink@mozilla.com John Hammink] (irc: jammink) | | [mailto:jhammink@mozilla.com John Hammink] (irc: jammink) | ||
|- | |||
| style="width:20%" | '''Gecko/WebAPI Lead''' | |||
| [mailto:gmealer@mozilla.com Geo Mealer] (irc: geo) | |||
|- | |- | ||
| '''Contributors''' | | '''Contributors''' | ||
Revision as of 23:48, 13 September 2012
Test Plan
Summary
| Gaia Lead | John Hammink (irc: jammink) |
| Gecko/WebAPI Lead | Geo Mealer (irc: geo) |
| 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