B2G/QA/Gaia Test Plan: Difference between revisions

From MozillaWiki
< B2G‎ | QA
Jump to navigation Jump to search
(Created page with "=Test Plan= == Summary == {| class="fullwidth-table" |- | style="width:20%" | '''Lead''' | [mailto:gmealer@mozilla.com John Hammick] (irc: jammick) |- | '''Contributors''' ...")
 
Line 29: Line 29:
== Current focus areas and needs ==
== Current focus areas and needs ==
* writing test plans based off of the specifications we have for features
* writing test plans based off of the specifications we have for features
* writing test cases and adding them to https://moztrap.mozilla.org/
* writing test cases and adding them to the [https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdFNvVGJnNHdCNERNaFpFbDE1RnJveGc#gid=23 feature test logs]
* testing particular areas and filing bugs
* testing particular areas and filing bugs
* verify that featured apps match their spec
* verify that featured apps match their spec

Revision as of 23:00, 3 August 2012

Test Plan

Summary

Lead John Hammick (irc: jammick)
Contributors Matt Brandt (irc: mbrandt)
David Clarke (irc: onecyrenus)
Status Pre-release, approaching Milestone 5
Tracker Pivotal Project
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 should be addressed.

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)

QA Lead Responsibilities

  • Writing exploratory test cases in moztrap
  • Writing writing test cases in moztrap
  • Running test cases
  • Ensuring the app meets it’s spec
  • Knowing the apps current status & progress
  • Communicate with dev leads
  • Know the tracking bugs -- nudging with necessary

App leads

contact:name / app / testcases / spec / link to additional documentation