MozillaWiki

QA/Test Plan Template: Difference between revisions

Page Discussion

QA/Test Plan Template (view source)

Revision as of 21:53, 3 May 2018

1,324 bytes added ,  3 May 2018
no edit summary
No edit summary
 
(23 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Approvals Required / Received'''
The following individuals are required to/have approved this Test Plan:
{| class="wikitable"
|-
! Name !! Title !! Department !! Approval Date !! Method
|-
|  || QA Reviewer || Product Integrity || Date || Email
|-
|  || Software Engineer || Engineering || Date || Email
|-
|  || EPM || Product Management || Date || Email
|}
'''Revision History'''
'''Revision History'''


This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded).  The description of the modification contains the differences from the prior version, in terms of what sections were updated and to what extent.
This section describes the modifications that have been made to this wiki page. A new row has been completed each time the content of this document is updated (small corrections for typographical errors do not need to be recorded).  The description of the modification contains the differences from the prior version, in terms of which sections were updated and to what extent.


{| class="wikitable" style="width:60%"
{| class="wikitable" style="width:60%"
Line 9: Line 25:
| 11/23/2015 || 1.0 || Brindusa Tot || Created first draft
| 11/23/2015 || 1.0 || Brindusa Tot || Created first draft
|-
|-
| || || ||  
| 10/05/2016|| 1.1 || Adrian Florinescu || Added point : 3.2 Channel dependent settings (configs) and environment setup
|-
| 02/28/2017|| 1.2 || Brindusa Tot ||  Move Risk Assessment and Coverage upper in the test plan, under the Test Strategy chapter
|-
| 05/09/2017|| 1.3 || Brindusa Tot ||  Update content based on new train model (without Aurora)
|-
| 06/08/2017|| 1.4 || Rares Bologa ||  Added 'Approvals' area
|}
|}


Line 45: Line 67:
  Specify Devices that need to be covered
  Specify Devices that need to be covered
  Specify other configuration/environmental setup needed
  Specify other configuration/environmental setup needed
== Channel dependent settings (configs) and environment setups ==
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
=== Nightly ===
<div class="mw-collapsible-content">
text
</div>
=== Beta ===
<div class="mw-collapsible-content">
text
</div>
=== Post Beta / Release ===
<div class="mw-collapsible-content">
text
</div>
</div>


= Test Strategy =  
= Test Strategy =  
== Test Objectives ==
== Risk Assessment and Coverage ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
This could be documented in bullet form or in a table similar to the one below.


{| class="wikitable"
{| class="wikitable"
|-
|-
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners
! ID !! Description / Threat Description !! Covered by Test Objective !! Magnitude !! Probability !! Priority !! Impact Score
|-
|-
| 1 || Name of the feature or sub-function being tested || The objective the test is trying to demonstrate || The criteria that will be evaluated to demonstrate the test is successful || Manual/Automation/Performance/Security/Telemetry || Eng Team
| RAC-1 || Risk description 1 || TO-1 || 2-Moderate || 1-Unlikely || 3-High || 6
|-
|-
| 2 || Repeat for each feature/sub-function || || || ||
| RAC-2 || Risk description 2 || TO-1 || 3-High || 3-Almost Certain || 3-High || 27
|-
|-
| 3 || || || || ||
| RAC-3 || Risk description 3 || TO-2 || 2-Moderate || 2-Possible || 3-High || 12
|}
|}


== Test types ==
'''Values:'''
Detail the testing levels expected to be applied and who is responsible for performing this testing (example below).


{|class="wikitable" style="width:60%"
* '''Magnitude:''' 1- Low , ''2-Moderate'', '''3-High'''
 
* '''Probability:''' 1-Unlikely, ''2-Possible'', '''3-Almost Certain'''
 
* '''Priority:''' 1 - Low, ''2-Medium'', '''3-High'''
 
'''Impact Score Breakdown:'''
* An impact value of 1, 2, 3, 4 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
* An impact value of 6, 8, 9, 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
* An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.
 
== Test Objectives ==
This section details the progression test objectives that will be covered. Please note that this is at a high level. For large projects, a suite of test cases would be created which would reference directly back to this master.
This could be documented in bullet form or in a table similar to the one below.
 
{| class="wikitable"
|-
|-
! Type of Testing !! Required (Yes/No) !! Owners !! Details/Comments
! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! RAC !! Owners  
|-
|-
| Manual
| 1 || Name of the feature or sub-function being tested || The objective the test is trying to demonstrate || The criteria that will be evaluated to demonstrate the test is successful || Manual/ Automation/ Regression/ Performance/ Usability/ Security/ Telemetry || RAC-1, RAC-2, RAC-3 || Eng Team
|style="text-align:center;" | Yes/No
|style="text-align:center;" |  ||
|-
|-
| Automation
| 2 || Repeat for each feature/sub-function || || || || ||
|style="text-align:center;" | Yes/No
|style="text-align:center;" | ||
|-
|-
| Regression
| 3 || || || || || ||
|style="text-align:center;" | Yes/No
|style="text-align:center;" | ||
|-
| Performance
|style="text-align:center;" | Yes/No ||  ||
|-
| Usability
|style="text-align:center;" | Yes/No ||  ||
|-
| Security
|style="text-align:center;" | Yes/No ||  ||
|-
| Metrics/Telemetry
|style="text-align:center;" | Yes/No ||  ||
|}
|}


Line 97: Line 133:
This section should contain links for builds with the feature -  
This section should contain links for builds with the feature -  
* Links for Nightly builds
* Links for Nightly builds
* Links for Aurora builds
* Links for Beta builds
* Links for Beta builds


Line 120: Line 155:
| QA - Nightly Testing  
| QA - Nightly Testing  
|style="text-align:center;" |  ||  
|style="text-align:center;" |  ||  
|-
| QA - Aurora Testing
|style="text-align:center;" |  || 
|-
|-
| QA - Beta Testing  
| QA - Beta Testing  
Line 139: Line 171:
| Test plan creation || Mozilla wiki
| Test plan creation || Mozilla wiki
|-
|-
| Test case creation || Google docs
| Test case creation || [https://testrail.stage.mozaws.net/index.php TestRail]/ Google docs
|-
|-
| Test case execution || Google docs
| Test case execution || [https://testrail.stage.mozaws.net/index.php TestRail]
|-
|-
| Bugs management || Bugzilla
| Bugs management || Bugzilla
|}
|}


= Status =  
= Status =  
== Overview ==
== Overview ==
  Track the dates and build number where feature was released to Nightly
  Track the dates and build number where feature was released to Nightly
Track the dates and build number where feature was merged to Aurora
  Track the dates and build number where feature was merged to Release/Beta
  Track the dates and build number where feature was merged to Release/Beta


== Risk analysis ==
 
Identify the high-risk assumptions
Identify existing bugs on the feature with high risk
Identify if other areas are affected by the fix
= References =
= References =
* List and links for specs
* List and links for specs
Line 164: Line 190:
   
   
= Testcases =  
= Testcases =  
== Overview ==
Summary of testing scenarios
== Test Areas ==
== Test Areas ==
{| class="wikitable" style="width:80%"
{| class="wikitable" style="width:80%"
Line 196: Line 219:
|style="text-align:center;" | ||  
|style="text-align:center;" | ||  
|-
|-
| Interraction (scroll, zoom)  
| Interaction (scroll, zoom)  
|style="text-align:center;" | ||  
|style="text-align:center;" | ||  
|-
|-
Line 204: Line 227:
| Usability and/or discoverability testing   
| Usability and/or discoverability testing   
|style="text-align:center;" |  || Is this feature user friendly
|style="text-align:center;" |  || Is this feature user friendly
 
|-
| RTL build testing 
|style="text-align:center;" |  ||
|-
|-
| '''Help/Support'''  
| '''Help/Support'''  
Line 323: Line 348:


== Test suite ==
== Test suite ==
  Full Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/192BDmxxPirNZMxaH8a9bN4ak1m0sp3U1PXT-G-THpWk/edit?usp=sharing link]
  Full Test suite - Link to test rail - testcases should be added under Firefox Desktop project [https://testrail.stage.mozaws.net/index.php?/suites/overview/17 link]
  Smoke Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/192BDmxxPirNZMxaH8a9bN4ak1m0sp3U1PXT-G-THpWk/edit?usp=sharing link]
  Smoke Test suite - Link with the tests - if available/needed.
  Regression Test suite - Link with the gdoc - if available/needed.
  Regression Test suite - Link with the tests - if available/needed.


= Bug Work =
= Bug Work =
Tracking bug – meta bug
Meta bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=12345 12345 - bug summary]


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
====== Logged bugs ( blocking [https://bugzilla.mozilla.org/show_bug.cgi?id=12345 12345] )======


====== Bug fix verification ======
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
{| class="wikitable" style="width:50%"
<bugzilla>
|-
    {
! Bug No !! Summary !! Status !! Firefox Verion
        "blocks":[12345],
|-
        "include_fields": "id, priority, component, assigned_to, summary, status, target_milestone"
|  123 || bug summary || NEW || Nighly 45
    }
|-
</bugzilla>
| || || ||
 
|}
</div>
</div></div>
</div>


<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
<div class="toccolours mw-collapsible mw-collapsed" style="width:auto">
 
====== Bug fix verification ======
====== Logged bugs ======
<div class="mw-collapsible-content">
<div class="mw-collapsible-content">
Bug 111111<br/>
<bugzilla>
Bug 211111<br/>
    {
        "blocks":[12345],
        "resolution":"FIXED",
        "include_fields": "id, priority, component, assigned_to, summary, status, resolution, target_milestone"
    }
</bugzilla>
</div>
</div>
</div>
</div>


= Sign off =
= Sign off =
== Criteria ==
== Criteria ==
Check list
Checklist
* All test cases should be executed
* All test cases should be executed
* Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
* Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
Line 366: Line 394:
List of OSes that will be covered by testing<br />
List of OSes that will be covered by testing<br />
*Link for the tests run
*Link for the tests run
** Daily Smoke, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Full Test suite, link to TestRail - Tests Runs and Results [https://testrail.stage.mozaws.net/index.php?/runs/overview/17 link]
** Full Test suite, use template from [https://docs.google.com/spreadsheets/d/1ch0OubyOWn1W-_JLF-38nvSvVB76Wmo1hkLccEtU5hk/edit?usp=sharing link]
** Daily Smoke, if needed/available
** Regression Test suite, if needed/available
** Regression Test suite, if needed/available
<br />


'''Merge to Aurora Sign-off'''
'''Merge to Beta Sign-off'''<br />
List of OSes that will be covered by testing<br />
List of OSes that will be covered by testing<br />
*Link for the tests run
*Link for the tests run
Line 392: Line 421:
|  Test Cases Creation  
|  Test Cases Creation  
|style="text-align:center;" |  ||  
|style="text-align:center;" |  ||  
|-
|  Full Functional Tests Execution
|style="text-align:center;" | 
|style="text-align:center;" | 
|-
|-
|  Automation Coverage ||
|  Automation Coverage ||
Line 406: Line 431:
|-
|-
|  Critical/Blockers Fixed and Verified || ||  
|  Critical/Blockers Fixed and Verified || ||  
|-
|  Daily Status Report (email/etherpad statuses/ gdoc with results) || ||
|-
|-
|  Metrics/Telemetry||  
|  Metrics/Telemetry||  
|style="text-align:center;" |  
|style="text-align:center;" |  
|-
|-
|  QA Signoff  - Nightly Release||  
|  Basic/Core functionality Nightly testing
|style="text-align:center;" | 
|style="text-align:center;" | 
|-
|  QA mid-Nightly Signoff||  
|style="text-align:center;" | Email to be sent  
|style="text-align:center;" | Email to be sent  
|-
|-
|  QA Aurora - Full Testing  
|  QA Nightly - Full Testing  
|style="text-align:center;" |  ||  
|style="text-align:center;" |  ||  
|-
|-
|  QA Signoff - Aurora Release ||  
|  QA pre-Beta Signoff||  
|style="text-align:center;"| Email to be sent  
|style="text-align:center;"| Email to be sent  
|-
|-
Line 424: Line 451:
|style="text-align:center;" |  ||  
|style="text-align:center;" |  ||  
|-
|-
|  QA Signoff  - Beta Release ||  
|  QA pre-Release Signoff ||  
|style="text-align:center;" | Email to be sent  
|style="text-align:center;" | Email to be sent  
|}
|}
Stephend
Confirmed users
9,511

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1108395...1193278"