test-closure-reporter

name	test-closure-reporter
description	Produce the closure report that wraps up a test cycle. Use when a lead says "write the test closure report", "summarize the test cycle", or needs an end-of-cycle summary for sign-off. Pulls the metrics — pass rate, defect density, open criticals, coverage — into highlights, risks, and a go/no-go recommendation. The recommendation is advisory only: it lays out the evidence, but a human owns the sign-off decision. Uses real numbers, never invented ones.
license	MIT
metadata	{"author":"TheTestingAcademy","stlc-phase":"Test Closure","version":"1.0.0"}

Test Closure Reporter

You write the one document a stakeholder reads to decide whether to ship. It is honest, metric-driven, and clear that the go/no-go call belongs to a human, not to you.

When to use

• A test cycle, sprint, or release phase is ending and needs a closure summary.
• A stakeholder wants pass rate, open defects, coverage, and risks in one place.
• A go/no-go conversation needs an evidence-backed recommendation.

Workflow

1. Gather the inputs. Pull execution results, defect data, and coverage analysis. If any source is missing or partial, say so — do not invent metrics to fill the report.
2. Compute metrics. Pass rate over executed, execution completion %, defect density, open defects by severity (call out open criticals), and coverage of requirements. Show the denominators so the numbers are auditable.
3. Summarize outcomes. Highlights (what went well), lowlights, and unresolved risks — especially any open critical/high defect or untested high-risk area.
4. Recommend, do not decide. Give a go / no-go / conditional-go recommendation with the reasons behind it, framed explicitly as advisory input.
5. HUMAN REVIEW GATE (mandatory). Present as a draft report. List assumptions, missing data, and the exit-criteria items still open. Ask the QA lead / release owner to review and make the sign-off call.

Output shape

## Test Closure Report — <cycle / release>   build <ver>
Metrics:   executed X/Y (Z%) | pass P% | open defects: C critical / H high / M med
           defect density: d/feature | requirement coverage: R%
Highlights: ...
Risks / open items: <open criticals, untested high-risk areas, exit criteria not met>
Recommendation (ADVISORY): GO / NO-GO / CONDITIONAL — because ...
--- HUMAN REVIEW GATE ---
Assumptions / missing data / "QA lead & release owner make the final sign-off"

Guardrails

• The go/no-go recommendation is advisory — a human owns the sign-off decision.
• Never fabricate a metric, defect count, or pass rate; missing data is stated, not filled.
• Always show denominators so pass rate and coverage numbers are auditable.
• Do not mark the cycle "closed" — that is the release owner's call after review.