QA/Test Plan Template

Overview

Purpose

Detail the purpose of this document. For example:

• The purpose of this document is to define:
• The test scope, focus areas and objectives
• The test responsibilities
• The test strategy for the levels and types of test for this release
• The entry and exit criteria
• The basis of the test estimates
• Any risks, issues, assumptions and test dependencies
• The test schedule and major milestones
• The test deliverables

Scope

This wiki details the testing that will be performed by the project team for the <project name> project. It defines the overall testing requirements and provides an integrated view of the project test activities. Its purpose is to document:

• What will be tested
• How testing will be performed

Ownership

What resources are needed, and when (developers, QA, PMs working on the feature)

Testing summary

Scope of Testing

In Scope

Detail what is in scope from a testing perspective for the project team.

Out of Scope

Detail what is out of scope from a testing perspective for the project team. Note: if usability testing is not in the scope of testing feature.

Requirements for testing

Environments

Specify OSes that need to be covered
Specify Devices that need to be covered
Specify other configuration/environmental setup needed

Test types

Owners must be identified beforehand

Type of Testing	Required (Yes/No)	Owners	Details/Comments
Manual	Yes/No
Automation	Yes/No
Regression	Yes/No
Performance	Yes/No
Usability	Yes/No
Security	Yes/No
Metrics/Telemetry	Yes/No

Status

Overview

Track the dates and build number where feature was released to Nightly
Track the dates and build number where feature was merged to Aurora

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

• List and links for specs

 List and links for available specs - documents, user stories, specifications

• Meta bug

Testcases

Overview

Summary of testing scenarios

Test Areas

Test Areas	Covered	Details
Private Window	[DONE]
Multi-Process Enabled	[IN PROGRESS]
Multi-process Disabled	[NOT STARTED]
Display (HiDPI)	N/A
Interraction (scroll, zoom)	N/A
Theme (high contrast)	N/A

Test suite

Full Test suite - Link with the gdoc
Smoke Test suite - Link with the gdoc
Regression Test suite - Link with the gdoc - if 

Bug Work

• Tracking bug – meta bug
• List of logged bugs
• Bug Verification

Schedule

The following table identifies the anticipated testing period available for test execution.

Project phase	Start Date	End Date
Start project
Study documentation/specs received from developers
QA - Test plan creation
QA - Test cases/Env preparation
QA - Nightly Testing
QA - Aurora Testing
QA - Beta Testing
Release Date

Sign off

Criteria

Check list

• All test cases should be executed
• Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
• All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)

Results

Nightly testing List of OSes that will be covered by testing

• Link for the tests run
  • Daily Smoke
  • Full Test suite
  • Regression Test suite

Merge to Aurora Sign-off List of OSes that will be covered by testing

• Link for the tests run
  • Full Test suite

Checklist

Exit Criteria	Status	Notes/Details
Testing Prerequisites (specs, use cases)
Testing Infrastructure setup
Test Plan Creation
Test Cases Creation
Full Functional Tests Execution
Automation Coverage
Performance Testing
All Defects Logged
Critical/Blockers Fixed and Verified
Daily Status Report (email/etherpad statuses/ gdoc with results)
Metrics/Telemetry
QA Signoff - Nightly Release		Email to be sent
QA Aurora - Full Testing
QA Signoff - Aurora Release		Email to be sent
QA Beta - Full Testing
QA Signoff - Beta Release		Email to be sent