QA/Test Plan Template: Difference between revisions
< QA
Jump to navigation
Jump to search
Brindusa.tot (talk | contribs) |
Brindusa.tot (talk | contribs) No edit summary |
||
| Line 18: | Line 18: | ||
= References = | = References = | ||
* List and links for specs | |||
List and links for available specs - documents, user stories, specifications | |||
* Meta bug | |||
= Requirements for testing = | = Requirements for testing = | ||
| Line 29: | Line 28: | ||
== Test types == | == Test types == | ||
Owners must be identified beforehand | |||
* Manual | * Manual | ||
* Automation | * Automation | ||
| Line 35: | Line 34: | ||
* Security | * Security | ||
* Metrics/Telemetry | * Metrics/Telemetry | ||
= Testcases = | = Testcases = | ||
== Overview == | == Overview == | ||
Summary of testing scenarios | |||
== Test suite == | == Test suite == | ||
- Link with the gdoc | Full Test suite - Link with the gdoc | ||
Smoke test suite - Link with the gdoc | |||
- Link with the gdoc | |||
= Bug Work = | = Bug Work = | ||
| Line 49: | Line 49: | ||
== List of logged bugs == | == List of logged bugs == | ||
== Bug Verification == | == Bug Verification == | ||
= Sign off = | = Sign off = | ||
| Line 56: | Line 57: | ||
* 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 | ||
* All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA) | * All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA) | ||
== Results == | == Results == | ||
Revision as of 08:36, 12 November 2015
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