QA/Firefox3/TestPlan/Template: Difference between revisions

< QA‎ | Firefox3‎ | TestPlan
No edit summary
 
No edit summary
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Feature <abc> Test Plan
<small>[[QA/Firefox3.1/TestPlan|&laquo; QA/Firefox3.1/TestPlan]]</small>
 
;Feature <abc> Test Plan


= Overview =
= Overview =


(Provide an abstract of the feature and the test strategy.  Are there particular challenges with testing this feature?)
  Provide an abstract of the feature and the test strategy.   
  Are there particular challenges with testing this feature?


= Scope of planned testing =
= Test Strategy =


(What do you plan to test?  What is covered by Developer testing?  What is not practical to test?)
  List major areas of test coverage
  List areas that will NOT be covered (by developer, third party, etc.)
  Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)


= Platform and Configurations =
= Schedule Scoping =
 
  Estimate amount of time it will take to complete feature
  (Consider nightly builds, security reviews, bugs turnaround time)


( Describe any particular OS platform, environmental configurations or FireFox configuration considerations)
= References =
 
= Major Test Areas =
 
(describe major test areas of the feature and major test cases.  Once the plan is done, these major test cases can be fleshed out into litmus or automated test cases)


= Schedule/milestones =
  Include notes, links, specs, relevant bugs


( Provide some breakdown of the major areas of the feature, how long it will take to develop or run the tests, and an approximate time this will be done.
= References =


(List useful links to the bug containing design info, feature meeting notes, wiki info, standards info, litmus group or subgroup, etc)
[[Category:Wikipage templates]]

Latest revision as of 17:45, 1 October 2014

« QA/Firefox3.1/TestPlan

Feature <abc> Test Plan

Overview

 Provide an abstract of the feature and the test strategy.  
 Are there particular challenges with testing this feature?

Test Strategy

 List major areas of test coverage
 List areas that will NOT be covered (by developer, third party, etc.)
 Describe how testcases will be created (litmus, mochitests, reftests, gristmill, etc..)

Schedule Scoping

 Estimate amount of time it will take to complete feature
 (Consider nightly builds, security reviews, bugs turnaround time)

References

 Include notes, links, specs, relevant bugs