What it does
Produces an ISTQB Test Status (Progress) Report for an in-flight release: gathers progress metrics, assigns an overall RED/YELLOW/GREEN status, and ends with corrective control recommendations. Distinct from the end-of-test Completion Report.
When to use it
During a sprint or release, to report testing progress and trigger corrective action (weekly or per milestone).
Prerequisites
qa.config.yml (paths, gates, risk_areas); ideally a TEST-PLAN-<release>.md baseline plus available results.
Output
ISO/IEC/IEEE 29119-3 Test Status Report -> docs/qa/STATUS-REPORT-<release>-<date>.md.
Mechanics
How it works
- Resolve the release and pull the Test Plan baseline
- Monitor: gather test-case progress, pass rate, defect and coverage metrics
- Control: recommend a corrective action with owner and date per deviation
- Escalate: assign overall RED/YELLOW/GREEN by top-down thresholds
- Output the Status Report with metrics tables and control recommendations
Why it works
The theory behind it
Test monitoring (gathering data), control (corrective action) and reporting; monitoring without control is just a dashboard, the report's value is the action it mandates.
CTFL v4.0 §5.3
Example
See it in use
> /qa:status-report R2.4✓ Correct when Compares progress to the plan with metrics plus control actions (mid-release).
Related commands
Used by