QAM Hub QAM Hub
Home / Glossary / Test plan

Test plan

Last reviewed

The document covering what will be tested for a specific release or project, by whom, in which environments, on what schedule, and what is explicitly out of scope. A plan is bounded and dated. It answers "what are we doing this time", which is a different question from the one a test strategy answers.

What it has to contain

A plan is useful when someone who missed the kickoff can read it and know what is being tested, where, by whom, until when, and what will not be tested. The out-of-scope list is the part teams skip and the part that prevents arguments at release time. Entry and exit criteria (what has to be true before testing starts, and what counts as done) turn the plan from a description into something you can check progress against.

Plan versus strategy

The test strategy sets the standing rules: how the organisation decides what to automate, which risks get deep testing, which environments exist. A plan applies those rules to one release. If every plan opens with three pages copied from the strategy, link to the strategy instead and keep the plan about this release.

Size follows risk, not habit

Standards such as ISO/IEC/IEEE 29119-3 describe a full test plan document, and regulated projects often need one. A two-week feature release in a product team usually does not. A one-page plan that is read beats a thirty-page plan that is filed. The test is whether the plan changes anyone's decisions.

A plan goes stale on day three

Scope moves, builds slip, a tester gets reassigned. A plan that is not updated becomes a record of intentions. Keep it short enough that updating it takes minutes, and keep the live status (what has run, what failed) in the test runs rather than in the document.

In QAM Hub

QAM Hub has no separate test plan document. The parts a plan tracks live in milestones, requirements linked to test cases, and the runs grouped under a milestone; the planning text itself stays wherever your team keeps documents. Traceability from requirement to result is explained in the requirements traceability matrix guide.

Back to the test management glossary