Software test plan template: free template for Confluence
An auditor or a customer asks one question about your tests: which requirements were tested, on which version, and what was the result? This test plan template is built around that question, with a traceability table you can fill as you go.
Test plan: [Product] [version]
Author: [name] · Approved by: [name, date] · Version under test: [build or version]
1. Scope
In scope: [features, requirements, platforms]. Out of scope: [what is not tested, and why].
2. Approach
Test levels: [unit / integration / system / acceptance]. Manual or automated: [split]. Regression: [which tests are re-run for each release].
3. Environment
[Test site or environment, configuration, data, tools and their versions.]
4. Entry and exit criteria
Start when: [build available, test data ready]. Done when: [all planned tests run, no open blocking defect, every requirement covered by at least one passed test].
5. Roles
Testers: [names]. Reviews and approves the results: [name].
6. Traceability
| Requirement | Test case | Result | Defect |
|---|---|---|---|
| [REQ-1] | [TC-1] | [Passed / Failed / Not run] | [link] |
| [REQ-2] | [TC-2, TC-3] | [Passed / Failed / Not run] | [link] |
7. Report and sign-off
Summary: [run, passed, failed, not run]. Open defects and their justification: [list]. Decision: [release / do not release], by [name, date].
How to use it in Confluence
- Click Copy the template, open a new Confluence page and paste: headings, lists and tables stay as they are.
- Replace the parts in [brackets] and delete what does not apply to you.
- To reuse it, save it as a space template: Space settings › Templates › Create template, then paste.
Where test plans usually fall short
- Requirements nobody tested. A list of passed tests says nothing about what was never tested. The traceability table makes the gaps visible.
- Results without a version. “Passed” is only meaningful with the build it was run on.
- No sign-off. For regulated software (for example under IEC 62304 for medical device software), someone must review and approve the results before release.
Related: Clearlane Tests and our validation support.