B2G/QA/Gaia Test Plan: Difference between revisions

From MozillaWiki
< B2G‎ | QA
Jump to navigation Jump to search
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
=Test Plan=
=Test Plan=
== Summary ==
{| class="fullwidth-table"
|-
| style="width:20%" | '''Lead'''
| [mailto:jhammink@mozilla.com John Hammink] (irc: jammink)
|-
| '''Contributors'''
| [mailto:mbrandt@mozilla.com Matt Brandt] (irc: mbrandt)<br/>[mailto:dclarke@mozilla.com David Clarke] (irc: onecyrenus)
|-
| '''Status'''
| Pre-release, approaching [https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdFNvVGJnNHdCNERNaFpFbDE1RnJveGc#gid=18 Milestone 4]
|-
| '''Tracker'''
|
|-
| '''Project Page'''
| [[B2G/QA]]
|-
| '''References'''
| Instructions for Contributors
|}


== Scope ==
== Current Focus Areas and Needs ==
 
* Writing test plans and cases based off of the specifications we have for features
== 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 [https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdFNvVGJnNHdCNERNaFpFbDE1RnJveGc#gid=23 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
* Writing exploratory test cases
* Testing particular areas and filing bugs
* Verify that featured apps match their spec
* Verifying and closing bugs with features & defects that have landed
* Running 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 ==
=== Email Templates ===
contact:name / app / testcases / spec / link to additional documentation
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email_Templates Email Templates]
 
=== Test Plans ===
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Email Email Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Browser Browser Test Plan]
* [https://wiki.mozilla.org/B2G/QA/Gaia_Test_Plan/Crash Crash Reporting Test Plan]

Latest revision as of 05:50, 22 April 2013

Test Plan

Current Focus Areas and Needs

  • Writing test plans and cases based off of the specifications we have for features
  • Writing exploratory test cases
  • Testing particular areas and filing bugs
  • Verify that featured apps match their spec
  • Verifying and closing bugs with features & defects that have landed
  • Running test cases

Email Templates

Test Plans

Retrieved from "https://wiki.allizom.org/index.php?title=B2G/QA/Gaia_Test_Plan&oldid=648250"