QA/Test Plan Template

Overview

Summary

This section will describe the feature and what should be tested. Provide a brief list of the target-of-test’s features and functions that will or will not be tested (user stories, specifications, etc).

Ownership

Should contain developers and QA, PMs

Status

Overview

Track the dates and build number were feature was released to Nightly
Track the dates and build number were 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

Requirements for testing

Environments

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

Test types

Owners must be identified beforehand

• Manual
• Automation
• Performance
• Security
• Metrics/Telemetry

Testcases

Overview

Summary of testing scenarios

Test suite

Full Test suite - Link with the gdoc
Smoke test suite - Link with the gdoc

Bug Work

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

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

List of OS that will be covered by testing Link for the tests run

• Daily Smoke
• Full test suite
• Regression suite