Test Procedures
A Test Procedure is the executable recipe for verifying requirements — how, where the Test Plan is what and why. A procedure groups one or more test cases; each case carries the numbered steps, expected results, pass/fail criteria, and a full operator-facing write-up.
Open it from the sidebar under Verify → Test Procedures, at /projects/:projectId/verification/test-procedures.
Procedure vs. test case — which fields go where
| Field | Belongs on | Why |
|---|---|---|
| Purpose / scope | Test Procedure | The intent and boundaries of this verification. |
| Status | Both | Procedure: Draft / Ready / In Progress / Approved. |
| Linked requirements | Both | The requirement(s) being verified. |
| Numbered test steps | Test Case | The ordered actions an operator follows. |
| Pass / Fail Criteria | Test Case | The concrete go/no-go for the scenario. |
| Expected Results | Test Case | The bar for "this scenario passed." |
| Preconditions | Test Case | The state the system must be in before running. |
| Procedure Workspace narrative | Test Case | The full operator write-up (rich text). |
Walkthrough
Create a procedure
- Open Verify → Test Procedures.
- Click Add Test Procedure.
- Give it a Title, set the Status (Draft / Ready / In Progress / Approved), and write the purpose and scope.
- Under Linked Requirements, check the requirement(s) the procedure verifies.
- Click Save. The procedure appears in the table with its object ID (for example
TP-000007).
Add test cases
- Select a procedure from the table.
- Click Add Test Case.
- Set the Title and Status, fill in Pass / Fail Criteria and Expected Results, and link the requirement(s).
- Enter the numbered steps in the step editor (one step per line).
- Write the full operator narrative in the Procedure Workspace — a rich-text word processor for the detailed write-up.
- Click Save.
Generate a starter case with AI
From the Requirements page, choose a requirement and use the AI test-case generator to draft a starter test case from the requirement text. Review and edit the result on the Test Procedures page before relying on it.
Run and re-run
When you are ready to execute, record a run from Test Executions (or the quick-log buttons on Test Case Detail). Each run captures a result (passed / failed / blocked / skipped), a build label, the executor, evidence links, and notes. If a case fails, fix the underlying issue and record a new run against the same case — every run is preserved as history.
Saving a run updates the requirement's verdict in the RVTM automatically.
Tips
- One procedure, many cases. A procedure groups the cases that verify the same requirement(s); each case carries its own steps and outcomes.
- Be specific about step outcomes. "Outputs the correct value" is not testable; "Outputs 42 ± 0.1 on the calibrated voltmeter" is.
- Capture evidence. Attach screenshots, logs, or measurements to each run.