Create a Test plan
Define the question, requirements, and reasons before running tests.
A Test plan keeps reusable requirements, rationale, settings, acceptance criteria, and evidence needs. Runs retain the plan revision they use.
State the context
In Testing, use the New menu to create a plan. Describe the product, question, recipient, and intended use of the result. Explain why each requirement matters.
Define how each requirement will be checked
Choose the verification method, settings, and criterion. Include work requiring manual review or evidence from outside executable tests. A baseline can gather information before you have acceptance criteria; an acceptance decision needs explicit confirmed criteria.
Check available capabilities
Your organization’s plan determines which testing capabilities are available. A Test plan can retain requirements outside that access. Preparing only the available subset requires explicit review; omitted tests remain recorded and the result stays partial.
Use a saved revision
Prepare a Run from the saved plan. From Testing & Evidence, Prepare Run adopts the exact saved proposal. Review changed requirements before using carried evidence or executing again.