Test summary report

End-of-cycle test results report. Coverage, pass/fail counts, defects found, and risk assessment.

520 wordsReportingSprintRelease

Test Summary Report ā€” Product Name / Sprint or Release

Report ID: TSR-XXX Prepared by: Name Date: YYYY-MM-DD Sprint / Release: Sprint X / v0.0 Report period: Start date ā†’ End date

Executive Summary

2ā€“4 sentences. State the overall quality signal: what was tested, what the pass rate was, whether the product is ready for the next stage, and the biggest risk or finding.

Test Coverage

Test Type Planned Executed Passed Failed Blocked Pass Rate
Functional X X X X X X%
Regression X X X X X X%
Exploratory sessions X X ā€” ā€” ā€” ā€”
Performance X X X X ā€” X%
Total X X X X X X%

Defects Summary

Severity Raised Fixed Closed Open
Critical X X X X
High X X X X
Medium X X X X
Low X X X X
Total X X X X

Open Defects

List defects that remain open at report date. Include ID, title, severity, owner, and status.

ID Title Severity Owner Status
BUG-XXX Title Sev Name Status

Test Environment Notes

Any environment issues that affected test results ā€” instability, downtime, data resets, etc.

Exploratory Testing Findings

Summarise findings from exploratory sessions that are not captured in formal test case results.

Risk Assessment

What risks remain? What coverage gaps exist? What should the next stage watch out for?

Risk Description Likelihood Impact Mitigated?
Risk Description H / M / L H / M / L Yes / No

Recommendation

Go / No-go / Conditional go ā€” and the reasoning.

Appendix: Not-executed Test Cases

List test cases that were planned but not executed, with reason.

Test Case ID Reason Not Executed
TC-XXX Reason

// Related templates

Test closure report

Sign-off report when testing completes. Final results, lessons learned, and recommendations.

Defect triage notes

Triage meeting agenda, defect prioritisation grid, and decisions log. For weekly QA syncs.

Test plan

Scope, approach, schedule, risks, entry/exit criteria. IEEE 829-style structure.