B2G/QA/Gaia Test Plan: Difference between revisions

From MozillaWiki
< B2G‎ | QA
Jump to navigation Jump to search
Line 1: Line 1:
=Test Plan=
=Test Plan=
== Summary ==
{| class="fullwidth-table"
|-
| style="width:20%" | '''Gaia Lead'''
| [mailto:jhammink@mozilla.com John Hammink] (irc: jammink)
|-
| style="width:20%" | '''Gecko/WebAPI Lead'''
| [mailto:gmealer@mozilla.com Geo Mealer] (irc: geo)
|-
| '''Contributors'''
|
* [mailto:mbrandt@mozilla.com Matt Brandt] (irc: mbrandt)
* [mailto:dclarke@mozilla.com David Clarke] (irc: onecyrenus)
* [mailto:nhirata@mozilla.com Naoki Hirata] (irc: nhirata)
* [mailto:tchung@mozilla.com Tony Chung] (irc:tchung)
* [mailto:krupa@mozilla.com Krupa Raj] (irc:krupa)
* [mailto:jshih@mozilla.com John Shih] (irc:jshih)
* [mailto:jsmith@mozilla.com Jason Smith] (irc:jsmith)
* [mailto:marcia@mozilla.com Marcia Knous] (irc:marcia)
|-
| '''Status'''
| Pre-release, approaching [https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdFNvVGJnNHdCNERNaFpFbDE1RnJveGc#gid=18 Milestone 4]
|-
| '''Tracker'''
| [https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdFNvVGJnNHdCNERNaFpFbDE1RnJveGc#gid=18 Feature Dashboard]
|-
| '''Project Page'''
| [[B2G/QA]]
|-
| '''References'''
| Instructions for Contributors
|}
== Strategy ==
== 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.
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.

Revision as of 05:48, 22 April 2013

Test Plan

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 and cases based off of the specifications we have for features
  • 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

Additional References

Email Templates

Test Plans