TemplateWord · 3 pages
Test summary report template
The report you share when testing ends: what was tested, the numbers, open bugs and your go or no-go advice, with example numbers that add up.
How to use this template. Grey italic lines tell you what to write. Yellow boxes and cells show an example for “Food delivery app, release 2.4”, the same project as the TesterPath test plan template. Replace them with your own numbers. Managers often read only section 1, so make it clear on its own.
Details at the top of the document
| Project | e.g. Food delivery app (Android, iOS and web) |
|---|---|
| Release / build | e.g. Release 2.4, final build 2.4.0 (412) |
| Test cycle | Start and end date, e.g. 09-11-2026 to 20-11-2026 |
| Prepared by | Name, role |
| Date | DD-MM-YYYY |
| QA recommendation | Go Go with known issues No-go |
1. Summary
Four or five lines: what was tested, the key numbers, the biggest open risk, and your recommendation.
Example: We tested release 2.4 from 09 to 20 Nov 2026. 186 of 192 planned test cases were run and 171 passed (91.9%). No Critical bugs are open. 2 Major bugs are still open in UPI autopay. Recommendation: go with known issues, with UPI autopay switched off by a feature flag until release 2.4.1.
2. What was tested
List the features in scope and say if each one was fully tested. Use the same list as the test plan.
| Feature / area | Tested? | Notes |
|---|---|---|
| Scheduled orders | Fully | All planned cases run |
| Reorder button | Fully | All planned cases run |
| UPI autopay | Partly | 4 cases blocked: payment sandbox down on 12 and 13 Nov |
| Regression: login, search, cart, payment, tracking | Fully | Automated suite plus a manual smoke test on the final build |
3. Test execution results
Planned = Run + Blocked + Not run. Run = Passed + Failed. Check that your numbers add up before you send.
| Area | Planned | Run | Passed | Failed | Blocked | Not run | Pass % |
|---|---|---|---|---|---|---|---|
| Scheduled orders | 64 | 64 | 60 | 4 | 0 | 0 | 93.8% |
| Reorder button | 38 | 38 | 36 | 2 | 0 | 0 | 94.7% |
| UPI autopay | 42 | 36 | 29 | 7 | 4 | 2 | 80.6% |
| Regression | 48 | 48 | 46 | 2 | 0 | 0 | 95.8% |
| Total | 192 | 186 | 171 | 15 | 4 | 2 | 91.9% |
Pass % = Passed ÷ Run × 100. Some teams divide by Planned instead. Say which one you used.
4. Bugs found
Count bugs by severity. Use the numbers from your bug tracker on the day you send this report.
| Severity | Found | Fixed and closed | Still open |
|---|---|---|---|
| Critical | 1 | 1 | 0 |
| Major | 6 | 4 | 2 |
| Minor | 9 | 7 | 2 |
| Trivial | 3 | 2 | 1 |
| Total | 19 | 14 | 5 |
5. Open bugs and known issues
List every open Critical and Major bug, and any Minor bug users will notice. Say what happens to each one.
| Bug ID | Title | Severity | Plan |
|---|---|---|---|
| BUG-231 | UPI autopay: mandate stays “Pending” after the bank approves it | Major | Fix in 2.4.1. Autopay hidden by feature flag until then. |
| BUG-238 | UPI autopay: cancel shows success, but the next payment is still taken | Major | Fix in 2.4.1. Same feature flag. |
| BUG-244 | Scheduled order time shows in 24-hour format on the receipt | Minor | Accepted by product owner. Fix in 2.5. |
6. Not tested, or changed from the plan
Be honest here. What did you skip, what was blocked, and what changed from the test plan? Give the reason.
Example:
- 4 UPI autopay cases were blocked because the payment sandbox was down on 12 and 13 Nov.
- 2 UPI autopay cases were not run: they need a real bank account, which QA does not have.
- Load testing was moved to release 2.5, as agreed in the test plan.
7. Environment and builds
Where the testing happened, so others can repeat it.
| Environment | Build | Browsers and devices |
|---|---|---|
| QA | 2.4.0 (398) to 2.4.0 (412) | Chrome, Firefox, Pixel 7 (Android 14), iPhone 13 (iOS 18) |
| Staging | 2.4.0 (412), final | Same as QA, plus Safari on Mac |
8. Risks and notes for the release
Anything the team should keep an eye on after release.
Example:
- Watch the payment failure rate on the dashboard for the first 48 hours.
- Customer support has a short note on the two known autopay issues.
9. Recommendation
Tick one option on the first page, then explain it here in 2 or 3 lines.
Example: Go with known issues. All Critical bugs are fixed, and regression passed on the final build. The two open Major bugs are in UPI autopay only, which stays switched off until 2.4.1.
10. Sign-off
The people below have read this report and agree with the decision.
| Name | Role | Date | Decision |
|---|---|---|---|
| QA lead | |||
| Development lead | |||
| Product owner |