Test plan

It is free to fill in online, needs no account, and downloads as a Word document or a PDF. See all IT and projects templates

• Product and release

  For example: TidyPlan mobile app 4.2.0

• Test lead

  For example: Anna Berg

• Plan version and date

  For example: 1.0, 3 March 2030

• What testing must show

  For example: That shared lists work for up to 6 people at once, that login and photo upload no longer crash and that nothing that worked before is broken.

• In scope

  For example: Shared lists, login, photo upload, notifications, the 20 key user journeys.

• Out of scope (optional)optional

  For example: Admin web panel, unchanged since 4.1.0. Tested only through the regression pack.

• Kinds of test

  One row for each kind of test.

  For example: Unit tests | Developers | On every change Integration tests | Developers | Daily Manual feature tests | Testers | Per feature Regression pack | Testers | Before release Performance test | Test lead | Once, 500 users at once Security check | Security lead | Once

• Environments and devices

  For example: Test server with copy of the live setup, without real customer data. 6 phones: 3 Android, 3 iOS, the oldest supported and the newest.

• Test data (optional)optional

  For example: Made-up accounts and lists. No real personal data.

• Schedule

  One row for each step.

  For example: Test plan agreed | 3 March Feature testing | 3 to 7 March Regression | 8 to 10 March Release decision | 11 March

• How bugs are handled

  For example: Each bug is logged with steps, screenshot and device. Critical: blocks release, fixed in 1 day. High: fixed before release. Medium and low: planned.

• Entry rules (when testing may start)

  For example: The build is on the test server, unit tests pass and release notes exist.

• Exit rules (when testing is done)

  For example: All planned tests run. No open critical or high bugs. Regression pack at least 98 percent passed. The test lead signs the report.

• Risks (optional)optional

  For example: Only 2 testers in the final week. Mitigation: developers join regression testing.

1. 11. Objectives
2. 22. Scope
3. 33. Kinds of test
4. 44. Environments and devices
5. 55. Test data
6. 66. Schedule
7. 77. Bugs
8. 88. Entry rules
9. 99. Exit rules
10. 1010. Risks

1. 01

   Fill in

   Type your details in the form. The document fills itself in as you type; click any gap to jump to its field.

2. 02

   Check

   Read it through. Gaps you have not filled stay marked, so nothing goes out half done.

3. 03

   Download

   Save it as a Word document to edit further, or as a PDF to send or print.

What details does this template ask for?

The form asks for 14 details, starting with Product and release, Test lead, Plan version and date, What testing must show, In scope. 3 more are optional.

Can I download this template as Word or PDF?

Yes. When you have filled in the form, save it as a Word document to keep editing, or as a PDF to send or print. It is free and needs no account.

Is what I type sent anywhere?

No. What you type stays in your browser while you fill in the document. It only goes to nerix if you choose to open the template in the chat.

Are these IT and project templates free?

Most are. Fill in and download them for free as Word or PDF, with no account. A few longer documents are premium: free to fill in, paid once to download, and marked with their price.

Does a security policy make us secure?

No document does that alone. A policy helps when it matches what people really do, so keep it short, explain it to your team and review it every year.

Is a project charter only for large projects?

No. A small project benefits too, because one page that names the goal, the limits and the decision maker prevents most arguments later.

• API integration specificationSpecify how two systems connect: what data moves, how it is secured, how errors are handled and who owns it.IT and projects
• Architecture decision recordRecord a technical decision with its context, options, reasons and consequences, for the team to find later.IT and projects
• Bring your own device policySet the rules for using personal phones and laptops for work: security, privacy, support and leaving.IT and projects
• Bug reportReport a software problem so a developer can repeat it, judge its impact and fix it.IT and projects
• Change management planPlan how people will be told, trained and supported through a big change, and how you will know it worked.IT and projects
• Change requestAsk for a change to a project or system, show its impact and record whether it is approved.IT and projects

See all IT and projects templates