• Stakeholders need a clear quality status for decision-making.
• Testing has progressed and results must be consolidated.
• Team needs transparent evidence for release or rollback decisions.

• Produce concise but evidence-based test reports.
• Translate test execution data into business-relevant risk status.
• Align teams on current quality, unresolved issues, and next actions.

1. Collect execution data: scope, pass/fail, defect distribution, blocked items.
2. Normalize metrics and remove noise from unstable runs.
3. Highlight critical findings and unresolved decision blockers.
4. Map defects to business impact and release risk.
5. Summarize trend vs. previous cycle.
6. Publish decision-oriented report with recommended actions.

Input:

• 420 cases executed, 12 open defects, 2 critical unresolved

Output:

• Report with risk summary, blocker ownership, and ETA confidence
• Recommendation: no-go until payment rollback defect resolved

Input:

• "Share testing progress"

Output (problem):

• Only pass rate shown, no risk context or blocker analysis
• Leadership cannot make release decision

• Do not report metrics without context and scope.
• Do not hide blockers behind aggregate pass rate.
• Do not mix verified facts with assumptions.
• Do not omit trend and change explanation.
• Do not provide go/no-go recommendation without clear evidence.