API Documentation
Docs + Word14 pages
Free
- Type
- Document
- Price
- Free
- Pages
- 9 · US Letter
- Style
- Minimal
- Difficulty
- Beginner
- Updated
- November 4, 2026
Every page (9)
Overview
A test plan decides when testing is finished and what risk remains when it stops. This template covers scope and exclusions, the approach by test level, environments, test data, a week-by-week schedule, entry and exit criteria with owners, and a risk register, so pass and fail are never a matter of opinion.
The sample is the plan for release 4.2 of the Orrindale Cloud billing console: 80% unit coverage, a load test at 1.5 times peak, a 5-medium-defect limit and sign-off on May 17, 2027. Replace the scope, thresholds, environments, schedule and risks with the ones your release manager will actually enforce.
Useful for
- A QA lead writing the test plan for a quarterly product release
- A release manager agreeing exit criteria and accepted risks before go-live
- A small engineering team formalising testing for its first customer audit
What's included
- Scope page with in and out of scope, assumptions and a callout on what is not covered
- Approach page with four test levels, coverage targets and a defect handling flow
- Environment setup reference with command, options and expected response
- Test data and coverage scorecard with masking, budget and defect escape rate
- Gantt schedule with owners, a code freeze and release milestone
- Entry and exit criteria, risk heat map and register, and a status page
How to use it
- 1
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
- 2
Replace the scope and out-of-scope lists with the features and platforms in your release, then set the coverage, defect and performance thresholds.
- 3
Describe your real environments and how test data is created and masked, then update the schedule with your cycles, freeze date and retest windows.
- 4
Name the sign-off owner, list the risks they accept by signing, and give every risk an owner and a response.
- 5
Delete the guide page, then share the plan with developers, the product owner and the release manager.
What you need
Requirements
- A Google account with access to Google Drive
Works with
- Google Docs
- Microsoft Word (download the .docx)
Questions
What should exit criteria include?
Defect thresholds by severity, regression and performance results, and a signed list of accepted risks. Avoid all tests pass on its own, because it hides open medium and low defects.
How do I decide what is out of scope?
List every feature, platform and test type you are not covering, with the reason. An explicit out-of-scope list stops untested areas looking covered.
Are the company and results real?
No. Orrindale Cloud, release 4.2, its people and every figure are fictional sample content. Replace all of it with your own product and thresholds.
- #test-plan
- #software-testing
- #qa-plan
- #exit-criteria
- #release-readiness
- #test-strategy
- #google-docs
Related templates
More Google Docs templatesMore developer workflows templates
Postmortem Review Deck
Slides + PowerPoint12 slides
Free
Annual Report
Docs + Word6 pages
Free
More test plan templates
See all 3
Mobile App Test Plan
Docs + Word7 pages
Free
Performance Test Plan
Docs + Word8 pages
Free
