B2G/QA/Gaia Test Plan: Difference between revisions

From MozillaWiki
< B2G‎ | QA
Jump to navigation Jump to search
Line 13: Line 13:
* [mailto:tchung@mozilla.com Tony Chung] (irc:tchung)
* [mailto:tchung@mozilla.com Tony Chung] (irc:tchung)
* [mailto:krupa@mozilla.com Krupa Raj] (irc:krupa)
* [mailto:krupa@mozilla.com Krupa Raj] (irc:krupa)
* [mailto:jshih@mozilla.com Jon Shih] (irc:jshih)
* [mailto:jshih@mozilla.com John Shih] (irc:jshih)
* [mailto:jsmith@mozilla.com Jason Smith] (irc:jsmith)
* [mailto:jsmith@mozilla.com Jason Smith] (irc:jsmith)
  |-
  |-

Revision as of 21:38, 6 August 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

App leads

app / testcases / spec / link to additional documentation