What it does
Produces the end-of-release Test Completion Report: gathers results by level, evaluates every exit criterion against gates to PASS/FAIL, states residual risk, confirms traceability, and applies a deterministic Ship/Hold decision rule.
When to use it
At the end of a release, to make the final ship/hold call (after go-no-go).
Prerequisites
qa.config.yml (paths, tooling toggles, gates, risk_areas, team); execution results in reports_dir; ideally the matching TEST-PLAN-<release>.md for exit criteria.
Output
ISO/IEC/IEEE 29119-3 Test Completion Report -> docs/qa/RELEASE-REPORT-<release>.md.
Mechanics
How it works
- Resolve the release and pull the Test Plan's Definition of Done
- Gather results by enabled level, marking missing measures not run
- Evaluate each exit criterion against gates as PASS/FAIL
- Produce the report with residual-risk and traceability statements
- Apply the deterministic Ship/Hold rule and name each failing gate
- Write the report referencing raw evidence
Why it works
The theory behind it
Test completion, the seventh process activity; residual risk is mandatory (Principle 1), you report what is not covered, never claim no defects remain.
CTFL v4.0 §1.4 · CTAL-TM · ISO 29119-3
Example
See it in use
> /qa:release-report R2.4✓ Correct when Evaluates exit criteria vs gates, states residual risk, and gives a ship/hold recommendation.
Related commands
Used by