Test Plan
The Test Plan is the strategy layer of verification. It captures what and why: the scope of testing, the verification methods you will use (Test / Analysis / Inspection / Demonstration), resources and environment, entry/exit criteria, and the schedule. It does not hold step-by-step instructions — those live on the Test Procedure page.
Open it from the sidebar under Verify → Test Plan, at /projects/:projectId/verification/test-plan.
What a Test Plan captures
Each test plan is a single artifact with these fields:
- Title — the plan's name.
- Status — Draft, In Review, Approved, or Archived.
- Objective — what this plan exists to achieve.
- Scope — what is and is not covered.
- Test Items / Coverage — which requirements or items are in scope.
- Approach and Environment — methods (Test, Analysis, Inspection, Demonstration), labs, simulators, and resources.
- Entry / Exit Criteria — when testing can start and what defines "done."
- Schedule Summary — phases of testing relative to project milestones.
Walkthrough
- Open Verify → Test Plan in the sidebar.
- Click Add Test Plan.
- Enter a Title and set the Status.
- Fill in the Objective, Scope, Test Items / Coverage, Approach and Environment, Entry / Exit Criteria, and Schedule Summary fields.
- Click Save. The plan appears in the table, identified by its object ID (for example
TPL-000001).
To revise a plan, click the edit (pencil) icon on its row. To remove one, click the delete (trash) icon and confirm.
When to use it
- After requirements are baselined.
- Before any test procedure is authored.
- Updated whenever scope, methods, or schedule change.
Tips
- Match method to requirement. Inspection for visible attributes, Analysis for engineering math, Demonstration for capability, Test for measured behavior.
- Keep the plan and procedures separate. The plan is what and why; the procedure is how.
- Write entry/exit criteria you can actually check. "All critical tests pass" and "no open critical defects" are verifiable; "system is ready" is not.