Test summary report writing documenting QA results and quality assurance findings for decision-making

Key takeaways

• A test summary report is a decision document, not a log. Open with the Go/No-Go verdict and put the pass rate further down. Release gatekeepers want a recommendation they can act on.

• Seven metrics cover most of the credibility gap. Pass rate, defect density, defect removal efficiency (DRE), defect leakage ratio (DLR), requirements coverage, automation flakiness and mean time to repair (MTTR).

• Production-ready benchmarks to hold a team to. Defect density < 1.0/KLOC, DRE > 90%, DLR on Sev-1/2 = 0%, flakiness < 1%, requirements coverage ≥ 95%, MTTR < 7 days.

• One page for the executive, an appendix for the auditor. A 2026-grade TSR fits on a single page for the CTO and product lead. Logs, traceability matrices and raw dashboards sit in linked appendices.

• Automate everything the humans don’t need to read. In 2026 the TSR narrative is AI-drafted from CI/CD signals, and the QA lead adds risk acceptance and the verdict. TSR prep drops from 4–6 hours to 30 minutes per release.

Updated November 2026: IEC 62304 Edition 2 status corrected (still a committee draft; the IEC forecasts publication in October 2028); new answers on test reporting and agile TSRs; Playwright test agents, ReportPortal agentic-run ingestion and DORA’s deployment rework rate added; TestRail and PractiTest prices re-checked.

Why Fora Soft wrote this playbook

Fora Soft has shipped 250+ products since 2005, many of them regulated and high-stakes: HIPAA telemedicine on CirrusMED, real-time video rooms for Netflix, HBO and EA on Speed.Space, concert-grade streaming for 10,000 concurrent viewers on Worldcast Live, and remote simultaneous interpretation on TransLinguist. Each of those releases passes through a test summary report before anyone presses deploy.

After a few hundred of those reports we settled on a template that holds up in front of founders, CTOs, compliance officers and customer security teams. This playbook is that template: the exact sections, metrics, thresholds, tooling and wording we ship to clients. All of it comes from real release meetings.

If you want the same pipeline on your codebase, with AI-drafted TSRs coming out of your CI every release and a live dashboard, our dedicated QA engineers ship it as a 3–4-week engagement, inside the same quality-testing process we run on every project.

Want a TSR template that your CTO actually reads?

30 minutes with our QA lead, your last release report, and we’ll show you the three sections to add, the two to delete, and how to automate the rest.

Book a 30-min call → WhatsApp → Email us →

What is a test summary report? The short answer

A test summary report (TSR) is a one-to-two-page document, written at the end of a test cycle, that states what was tested and what was not, the results against agreed exit criteria, the open risks, and a Go/No-Go recommendation for the release. In testing, “TSR” is simply the abbreviation for test summary report; some teams call the same document a test closure report. ISTQB’s current Foundation syllabus (CTFL v4.0.1, 2024) and ISO/IEC/IEEE 29119-3:2021 call the same artifact a test completion report; the version you send during the cycle is the test progress report.

A test summary report in software testing (TSR) is the one artifact that turns test execution data into a release decision. It is not the daily standup update, not the defect list and not the release notes, and mixing them up is why most TSRs get ignored.

Artifact Purpose Audience Timing
Test Summary Report Release decision + risk assessment CTO, PM, release manager, compliance End of test cycle
Daily test status Live progress + blockers QA team + developers Daily standup
Test execution report Every test result, duration, env QA engineers, devs Per run
Defect log Individual bug tracking Developers, triage Continuous
Release notes New features + known limitations Customers, product On release

Test reporting is the practice of turning test results into documents that people act on. In software testing it produces the five kinds of test reports in the table above: daily status, per-run execution reports, defect logs, release notes and the test summary report, which is the only one that ends in a release decision.

The TSR pulls data from every other artifact for one purpose: to answer “should we ship?” with evidence. Each sentence either supports the verdict or qualifies it.

Rule of thumb: if a reader can’t infer the Go/No-Go recommendation from the first 200 words, the TSR is a log, not a report.

The Minto-pyramid TSR template (one page)

The test summary report template our clients read most is a single page. Executives and release managers scan rather than read. The Minto-pyramid version gives the answer first, then the supporting facts, then the details.

Anatomy of a one-page test summary report: verdict first, then seven metrics vs targets, then linked appendices

Figure 1. A one-page TSR in Minto order: the verdict up top, the seven metrics in the middle, everything else linked below.

TEST SUMMARY REPORT — Release X.Y
Build: 2026.07.28.1   Date: 2026-07-28   Cycle: Sprint 42
Scope:   Web app + iOS/Android clients: payments, auth, onboarding
Not tested: Legacy admin panel (frozen, no changes this release)
Env:     Staging with prod-like data, device lab (6 devices), 2 regions

VERDICT    [ ] GO    [x] GO WITH DEFERRALS    [ ] NO-GO

Summary (1 sentence):
  Release X.Y meets all Must-Pass exit criteria; two Medium defects deferred
  post-launch with hotfix queued and feature-flag mitigation.

METRICS
  Tests executed ........... 148/150 (98.7%)
  Pass rate ................ 94.0%   (target ≥ 95%, acknowledged)
  Defect density ........... 0.8 per KLOC   (target < 1.0)
  DRE ...................... 94%            (target > 90%)
  DLR  Sev-1/2 ............. 0%             (target 0%)
  Requirements coverage .... 95%            (target ≥ 95%)
  Automation flakiness ..... 0.3%           (target < 1%)
  MTTR (this cycle) ........ 3.1 days       (target < 7)

TOP RISKS
  1. Medium defect — payment retry edge case. Mitigation: feature
     flag off at launch; hotfix ready Monday.
  2. Medium defect — iOS 16 visual regression on rare screen size.
     Mitigation: affects < 0.4% of MAU; regression scheduled Sprint 43.

EXIT CRITERIA
  [x] Zero unresolved Sev-1/2 defects
  [x] ≥ 95% requirements tested and passed
  [x] Automation flakiness < 1%
  [x] Performance within ± 5% of baseline
  [x] Security regression suite green

SIGN-OFF    QA Lead ___  Product ___  Release Mgr ___  Compliance ___

Appendix (linked):  Defect log   Traceability matrix   Dashboards

Why this works. This is a filled-in test summary report example you can copy as-is. The verdict comes first. Scope and what was not tested sit right under the build line, so nobody mistakes silence for coverage. Seven numbers fit in one glance. Each risk has its mitigation next to it, so a skeptical reader sees what the team has already covered. The sign-off list at the bottom makes accountability explicit, and appendices are links rather than pasted content.

The Go/No-Go verdict: how to make the call

A verdict needs evidence behind it. Write the exit criteria before the test cycle starts and compare them with reality at the end; the difference is the verdict.

Go. Every Must-Pass criterion met. Each deferred item has a named owner, a mitigation, and a fix date.

Go with deferrals. All critical/high defects resolved; 1–3 Medium defects deferred with documented risk acceptance and a shipped mitigation (feature flag, fallback, monitoring alert).

No-Go. Any unresolved Sev-1 or unmitigated Sev-2 defect. Test flakiness above 5%. Requirements coverage below 80%. Escaped defect from last release still unresolved. Any single one triggers a hold.

A sample No-Go rationale. “Three unresolved Sev-1 defects (auth bypass, data loss on retry, cold-start crash on iOS 17). Automation flakiness 6.2% this cycle, so the regression signal is untrustworthy. Requirements coverage 78%. Hold release; estimated 5-day delay for Sev-1 fixes plus test-suite stabilization.”

Go/No-Go gate: Sev-1, coverage under 80%, flakiness over 5% or an unfixed escape force No-Go; then Go or Go with deferrals

Figure 2. The Go/No-Go call as a gate: walk the checks top-down and the first failed one sets the verdict.

Reach for a “Go with deferrals” verdict when: the business case for shipping on time outweighs the deferred risk and you have a visible mitigation. If you can’t name the mitigation in one sentence, the right call is No-Go.

The seven metrics that matter

Pick these seven and keep them quarter after quarter, and the TSR almost writes itself. Every other number is context.

Metric Formula Green Red
Pass rate Passed / Executed ≥ 95% < 85%
Defect density Defects / KLOC < 1.0 > 3.0
DRE Found pre-release / Total > 90% < 75%
DLR (Sev 1–2) Escaped / Total 0% > 2%
Requirements coverage Requirements tested / Total ≥ 95% < 80%
Automation flakiness Flaky runs / Total runs < 1% > 5%
MTTR Mean days to fix < 7 > 21

Why these seven. Pass rate and coverage show how much ground you covered, and defect density and DRE show how well. DLR and MTTR tell you whether the team learns from escapes. Automation flakiness tells you whether the whole signal can be trusted at all.

Seven test summary report metrics with green ship-ready targets and red danger thresholds: pass rate, DRE, DLR, coverage

Figure 3. The seven metrics as a scan-in-five-seconds scorecard: green is the ship target, red is the number you must explain in the verdict.

Pair defect density with coverage, always: a 97% pass rate with 40% requirements coverage means you tested half the product well. One number is never a verdict, so read the pair.

Defect density, DRE, DLR explained

Defect density. Defects found divided by thousand lines of code (KLOC). A mainstream production codebase runs 0.5–1.5 per KLOC. Below 0.5, either you shipped rock-solid code or your tests didn’t exercise the surface area; read both numbers together (if requirements coverage is also low, it’s the second). When density stays above 3.0 per KLOC release after release, the problem usually sits in the code rather than in the tests, and our code audit service lists every issue with file, line and fix within three business days.

Defect Removal Efficiency (DRE). Defects caught in testing divided by total defects (testing + production). > 90% for mature orgs, > 95% for regulated industries. If DRE drops below 85%, look at test scope and shift-left practices: too many bugs are reaching users.

The benchmarks come from data. In Capers Jones’ defect-removal research, teams that don’t measure DRE almost always sit below 85%, the US average hovers around 85% (a 15% escape rate), and he treats anything under 95% cumulative DRE as inadequate software-quality practice. Testing alone rarely gets you past 95%: you need formal design and code inspections on top, since most single test types catch under half of the defects present. Cite the source in the TSR (Jones, Software Defect Removal Efficiency) so the number carries weight in a review.

Defect Leakage Ratio (DLR). The mirror of DRE: bugs that escaped to production divided by total bugs. Segment by severity: DLR on Sev-1/2 should be 0%. Period. Track DLR on Sev-3/4 as a quality trendline, allow a few percent, and alert on sustained growth.

Put all three into the TSR every cycle. A sliding DRE with flat defect density is an early sign of test scope drift. Catch it here, before it turns into a customer incident you read about on the bug-crisis escalation flow.

DRE versus DLR: defects caught in testing versus escaped to production, with Capers Jones cumulative DRE benchmark bands

Figure 4. DRE counts what testing caught; DLR counts what reached users. Benchmark bands are from Capers Jones’ defect-removal research.

Coverage and traceability: what “tested” really means

“We tested it” means nothing without a denominator. The TSR shows three coverage numbers:

Requirements coverage. For every acceptance criterion in the release, is there at least one passing test that asserts it? Target ≥ 95%. Below 80% the TSR is unreliable, because you can’t tell green from unchecked.

Code coverage (branches or lines). Target ≥ 80% on high-risk paths (authentication, payments, PHI, video encoding). Branch coverage says more than line coverage. Both can be gamed, so add mutation testing on critical code.

Workflow coverage. The user-facing scenarios listed in your test plan. Target 100% of critical workflows and ≥ 90% of secondary ones. The product team watches this number; the first two are for engineering.

Traceability matrix. A linked artifact (not embedded in the TSR) that maps every requirement to its test cases and each test case’s latest result. Xray, Zephyr, TestRail and PractiTest all render this in a live view; export a static snapshot for the release archive.

Automation health: flakiness, ROI, time-to-signal

Automation coverage. Percentage of test cases automated. Target 70–85%. 100% is rarely the goal, since visual, exploratory and accessibility tests stay with people.

Flakiness rate. The share of test runs that fail intermittently without a code change. Above 5% is a red flag; at 1% the suite stays trustworthy. Move flaky tests to a separate quarantine suite to keep the main signal clean, and report the quarantine size in the TSR.

Time-to-signal. Minutes from a merged PR to a green CI answer. Target < 30 minutes for gating tests and < 2 hours for nightly suites. When the signal is slow, people merge without waiting and main breaks.

Automation ROI. Hours of manual regression avoided divided by hours spent maintaining automation. Report it quarterly. A healthy suite lands between 3:1 and 5:1 after 12 months; below 1:1 it costs more than it saves.

You can pull most of these straight from CI metadata. We write a thin AI layer on top of the raw runs that summarizes flakiness, groups failures by root cause and drafts the narrative for the TSR.

Automating your TSR end-to-end?

Our Agent Engineering stack drafts the TSR narrative, pulls live metrics, and files the Jira ticket with a Go/No-Go recommendation — the draft lands in under 5 minutes, and the human review fits in the rest of the 30.

Book a 30-min call → WhatsApp → Email us →

Performance test report executive summary and execution summary template

A performance test report executive summary answers one question in a few lines: did the system hold the target load inside its service-level objectives (SLOs), and if not, where did it break first? Lead with the verdict, then the load profile, the three SLO numbers (p95 latency, error rate, throughput), the first bottleneck and the recommendation. Graphs and raw k6, JMeter or Gatling output go to the appendix.

PERFORMANCE TEST — EXECUTIVE SUMMARY — Release X.Y
Verdict: GO WITH DEFERRALS (launch capped at 2,000 users)
Load profile: 2,000 concurrent users, 15-min ramp, 60-min soak

  p95 API latency ...... 410 ms     (SLO ≤ 500 ms)    PASS
  Error rate ........... 0.12%      (SLO < 0.5%)      PASS
  Throughput ........... 1,850 rps  (target 1,600)     PASS
  p95 at 2.5x load ..... 1,240 ms   (SLO ≤ 500 ms)    FAIL

First bottleneck: primary DB CPU at 92% above 4,500 users
Recommendation: add 2 read replicas; re-run 2.5x test before lifting cap

The numbers above are illustrative; plug in your own SLOs. Keep the comparison with the last baseline run in the same block (±5% is our default tolerance), because a regression against last week’s build matters more to the release decision than an absolute number.

Test execution summary report template. For an automation run or a single test cycle, a table beats prose. One row per suite, the same columns every time:

Suite Total Passed Failed Blocked / skipped Flaky (quarantined) Duration
Unit 4,812 4,809 3 0 0 6 min
API 1,140 1,128 9 3 4 14 min
E2E web 312 298 8 6 5 22 min
Mobile (6 devices) 186 179 4 3 2 38 min

Total = passed + failed + blocked/skipped; quarantined flaky tests run in a separate suite and are not counted in Total. Keep blocked and skipped tests apart from failed ones, and quarantined flaky tests apart from both. That separation decides whether an automation test results template informs a Go/No-Go or hides problems. Test-management and reporting tools such as TestRail, Xray, Allure and ReportPortal produce these counts per run, so nobody should type the table by hand.

IEEE 829 and ISO 29119-3 sections

When a customer audit, compliance review or enterprise security questionnaire arrives, the one-page TSR isn’t enough. Many articles get the standard wrong: IEEE 829-2008 was withdrawn and superseded by ISO/IEC/IEEE 29119-3 (current edition 2021), where the release-level report is called the Test Completion Report. The section layout below (the classic IEEE 829-1998 test summary report) is still the practical reference, and 29119-3 maps to it almost one-for-one. If an auditor asks which standard you follow, name 29119-3, not 829. The ISTQB glossary uses the same terms; the eight sections are:

1. Test summary report identifier. Release/build ID, cycle, author, date.

2. Summary. Scope: what was tested, in which environments, by whom. Pass/fail ratio, defects open/closed. Verdict.

3. Variances. Anything that deviated from the test plan: deferred tests, unavailable environments, scope changes mid-cycle.

4. Comprehensive assessment. Whether the product meets exit criteria on the seven metrics above. Risk acceptance is discussed here in detail.

5. Summary of results. Aggregated test data by suite: functional, regression, security, performance, accessibility, compliance.

6. Evaluation. Quality assessment vs requirements. Trend vs previous release.

7. Summary of activities. Resources used: tester-days, environments, external vendors. Useful for quarterly ops review.

8. Approvals. Signatures: QA lead, product owner, release manager, and (for regulated) compliance officer, security lead.

Audience tailoring: CTO vs product vs customer

For the CTO or tech lead. Open with the automation-health metrics and the defect-density trend, then technical debt signals and test-stack ROI. Keep the verdict, but stress the architecture-level risks.

For the product manager. Open with requirements coverage and workflow coverage, then the severity breakdown with business impact: which user stories shipped clean and which shipped with a mitigation.

For the QA lead. The full report, with a lessons-learned section at the end: what surprised us, what we changed mid-cycle, what goes into next sprint’s retro.

For the customer or regulator. A sanitized version without internal velocity metrics. Focus on compliance verification, SLA metrics, known limitations and documented mitigations. For SOC 2 or HIPAA audits, include the evidence chain as well (links to immutable logs).

That makes one TSR with four renders. Generate them from the same data source, or within a quarter they will contradict each other.

Visualizing results: dashboards, trends, heat maps

Pass/fail trend. A line chart of pass rate across the last 10 cycles. Spikes and dips point to stories the table hides.

Defect burndown. Open defects by severity against days left in the release. A flat line here means defects are piling up, so escalate.

Coverage heat map. A grid of modules by test coverage. Red cells are your next sprint’s priority; they also answer the “what did you not test” question in audits.

Severity pyramid. A stacked bar of Sev-1/2/3/4 defects across the last 5 releases. Slow growth in the Sev-3/4 tier is an early warning of scope drift, even while Sev-1/2 stays at zero.

Host the charts in the tool the team already uses for tickets. Executives never open a separate reporting URL; the CTO wants the dashboard inside Jira, Linear or GitHub.

Tooling: what to use in 2026

Tool Category Pricing Best for
TestRail Test management, live dashboards From $38/user/mo (Professional, annual); Essentials $22 for up to 5 users General-purpose QA teams
Xray for Jira Jira-native test mgmt, coverage macros ~$6/user/mo, bills all Jira seats Jira-heavy shops; regulated orgs
Zephyr Scale Jira-native test mgmt + execution analytics From $10/mo up to 10 users, then per user; bills all Jira seats Automation-heavy teams
BrowserStack Cloud test lab + reporting From $29/mo (Live Desktop, billed annually) Mobile + cross-browser coverage
PractiTest Test mgmt, API-first $47/user/mo (Team plan) Custom reporting, enterprise audit
Momentic / QA Wolf / Testim AI-generated tests + auto-summaries Quote-based; QA Wolf bills per test per month Teams reducing manual regression
Your CI + Python + LLM Custom AI-drafted TSR Infra + LLM tokens Teams that want full control

TestRail (Essentials $22, Professional $38, Enterprise $78 per user per month, billed annually) and PractiTest prices re-checked on vendor pages in November 2026; BrowserStack checked in October 2026; Xray and Zephyr: Atlassian Marketplace tiers as of mid-2026. Jira apps bill on your whole Jira user tier, not only on testers, so a 200-seat Jira instance pays for 200 Xray seats.

Our default stack. TestRail or Xray holds test cases and runs. A small Python job in CI pulls the metrics, has an LLM draft the narrative and posts the TSR to Jira and Slack. A person edits the risk section and presses approve. Preparation takes 30 minutes per release instead of 4–6 hours.

What changed in AI test tooling. Playwright now ships three test agents: Planner writes a Markdown test plan, Generator turns it into test files, and Healer repairs failing tests or skips them when the feature looks broken. ReportPortal 26.0.3 (June 2026) ingests results from agentic testing runs alongside classic automation launches. Give AI-generated and healed tests their own row in the execution summary, because a test the Healer patched or skipped is weaker evidence than one that passed unchanged.

Why a person still signs the verdict. Google’s 2025 DORA (DevOps Research and Assessment) report found that 90% of software professionals now use AI at work, yet only 24% trust its output a lot or a great deal. An AI-drafted TSR saves hours. An AI-accepted risk is a liability nobody owns.

Reach for the build-it-yourself CI + LLM TSR when: you release weekly or faster, your metrics already live in CI, and you want the narrative drafted automatically. If your test cases still live in spreadsheets, buy a test-management tool first and automate the reporting once the data is clean.

TSRs for regulated industries (HIPAA, SOC 2, IEC 62304, EU CRA)

HIPAA and medical (IEC 62304). Add a risk classification by patient-safety impact. Each regulatory requirement needs a test, a test result, and an immutable evidence log entry with timestamp and operator identity. TSR sign-off expands to include the compliance officer and, for clinical releases, a qualified clinical reviewer. For US medical device software, the FDA’s Quality Management System Regulation (QMSR) took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference, so point the TSR at the design-verification records of ISO 13485 clause 7.3.6. IEC 62304 Edition 2 is still a committee draft: the first draft drew almost 1,500 comments, a second committee draft was due in 2026, and the IEC forecasts publication in October 2028 (Johner Institute, July 2026). The draft swaps safety classes for two process rigour levels, so until it is published keep reporting against IEC 62304:2006+A1:2015 and its software safety classes A, B and C.

SOC 2 Type II. The TSR becomes an evidence artifact for the annual audit. Verify the security controls explicitly: encryption in transit and at rest, access control, audit logging, session management, password policy. Archive the last 12 TSRs immutably, because auditors sample them.

Financial / PCI. Report payment-flow test results explicitly, using synthetic card data, and add a separate section on network-segmentation verification. We documented a real workflow in how we test payment systems for reliability. For EU banks, insurers and payment firms, the Digital Operational Resilience Act (DORA) has applied since 17 January 2025 and requires a documented resilience-testing programme; archive each TSR as part of that evidence.

GDPR and EU privacy. Data-subject-rights tests (export, delete) need passing results and evidence. Record data-residency verification per region.

EU Cyber Resilience Act (CRA). Since 11 September 2026, manufacturers of products with digital elements sold in the EU must report actively exploited vulnerabilities and severe incidents through ENISA’s Single Reporting Platform: an early warning within 24 hours and a notification within 72 hours, then a final report within 14 days after a fix is available for an exploited vulnerability, or within one month for a severe incident (European Commission). Give the TSR a security section that lists open vulnerabilities by severity, their exploit status and the fix release, so the release decision and the reporting clock run on the same data.

Reach for the full ISO 29119-3 completion report when: HIPAA, SOC 2, PCI or IEC 62304 is in scope. The one-page version wins the release meeting; the audit wants the section-by-section version with an immutable evidence chain.

TSRs for specific verticals

Mobile (iOS / Android). Add device coverage (at least four: low-end, mid-range, flagship, tablet), OS coverage (two major versions), crash rate (< 0.1% per session), and network profile results (Wi-Fi / 4G / 3G / offline). iOS automation has its own flakiness profile worth calling out separately.

WebRTC and streaming. Add the seven WebRTC metrics (bitrate, FPS, packet loss, RTT, jitter, freeze ratio, A/V sync) with green/yellow/red bands, plus the concurrent-session peaks you tested. The encoding metrics behind them live in our video encoding track; see how we test WebRTC stream quality for the full metric definitions.

E-learning / SaaS. Add completion-flow checks (progress save, quiz accuracy, certificate generation), WCAG 2.2 AA accessibility results, and performance budgets (page load < 2 s, video buffer < 2 s).

E-commerce. Add cart and checkout test coverage per region, payment gateway results per processor, and peak-load numbers. Payment defects default to Sev-1. Add WCAG 2.2 AA results here too: the European Accessibility Act has covered e-commerce sold in the EU since 28 June 2025.

Mini case: catching a Sev-1 in the TSR review, not in production

Situation. A SaaS client was on a weekly release cadence with a simple Google Doc TSR that listed pass counts only. Three releases in a quarter shipped with Sev-1 escapes. DLR on Sev-1/2 had drifted to 4.7%. The exec team was ready to slow releases to monthly and put a 10-day manual QA gate in front of every deploy.

Plan. In a 3-week engagement we replaced the Google Doc with an automated Minto-pyramid TSR generated from CI, covering seven metrics, the severity breakdown, a traceability matrix and a Go/No-Go recommendation. At release-candidate freeze the TSR posted itself to Jira and Slack, and the QA lead spent 20 minutes adding risk acceptance and signing off.

Outcome. On release 4, the automated TSR surfaced an unresolved Sev-2 defect in the payment retry path, together with a DRE regression. The team held the release for 48 hours, fixed the defect and shipped. Over the next quarter DLR on Sev-1/2 dropped to 0%, DRE climbed from 82% to 94%, and the weekly cadence resumed. Release meetings shrank from 90 minutes to 20 minutes. The executive team kept the weekly cadence and shelved the 10-day gate proposal.

If you want the same outcome, book 30 minutes and bring one recent TSR. We’ll show you the three gaps.

Five common mistakes that destroy TSR credibility

1. Vanity metrics. “97% pass rate” with 40% requirements coverage means you tested half the product well. Always pair pass rate with coverage and defect density.

2. Burying bugs in the appendix. Sev-1/2 issues belong above the fold, each with a mitigation sentence. A TSR that hides its worst news loses the room at the next release.

3. Counting blocked tests as passed. Pass, Fail, Blocked and Not Executed are four different buckets. A test blocked by a broken environment says nothing about quality, and reporting it as a pass will cost you credibility the day someone checks.

4. No context for the verdict. A bare “GO” is worthless in a regulatory audit and invites suspicion in a customer review. Spell out which exit criteria passed, what was deferred and why the residual risk is acceptable.

5. Hand-crafting the TSR every cycle. If the QA lead spends half a day on formatting, the report is out of date by the time it ships. Automate everything that needs no human interpretation and leave people only the verdict and risk paragraphs.

Hand-crafting your TSR every Friday?

We’ve automated this on a dozen client codebases. Three weeks from kick-off to a TSR that ships itself with every CI run.

Book a 30-min call → WhatsApp → Email us →

A decision framework — pick your TSR depth in five questions

1. How often do you release? Weekly or faster → automated one-page TSR per release. Monthly → automated one-page + expanded ISO 29119-3 completion-report appendix. Quarterly → full ISO 29119-3 completion report every cycle.

2. Is the product regulated? HIPAA, SOC 2, PCI, IEC 62304 → ISO 29119-3 completion report with compliance section and immutable evidence chain, always. Unregulated B2B SaaS → one-page TSR is enough.

3. Who reads the TSR today? If it’s only the QA lead, the TSR has failed its purpose; send it to the CTO, product and release manager by default. If customers read it, ship a sanitized external version alongside.

4. How much of testing is automated? < 50% → the TSR reads like an execution log, so put automation ahead of reporting polish. 50–80% → an AI-drafted TSR pays back immediately. > 80% → the TSR is mostly a triage of flakiness and coverage gaps.

5. Does the TSR trigger any decision? If not, delete it and save the hours. A TSR nobody acts on is ceremony: it costs real QA minutes and pulls executive attention away from reports that matter.

KPIs: what to report to the business

Quality KPIs. DRE (target > 90%), DLR Sev-1/2 (target 0%), defect density (target < 1.0/KLOC). The quarter-over-quarter trend tells you more than absolute values.

Business KPIs. Release cadence (releases/week), on-time release rate (> 95%), escaped-defect impact in $ (revenue lost, support cost). Attach a rolling 90-day view.

Reliability KPIs. Flakiness (< 1%), time-to-signal (< 30 min for gating suite), automation ROI (> 3:1 after 12 months), MTTR (< 7 days). If you already track DORA metrics, add change failure rate and deployment rework rate: DORA added rework rate to its Quick Check benchmarks in April 2026.

When NOT to write a full TSR

Pre-PMF startups. Before product-market fit, a Slack message in the release channel is enough reporting. Ceremonial TSRs burn engineering hours that belong to the product.

Internal tools with no compliance exposure. Git diff, CI status and a smoke test are enough. A formal TSR for an internal CLI is overkill.

Continuous-deployment teams with strong monitoring. When a product ships every hour with feature flags and instant rollback, the TSR moves to the monitoring dashboard and turns into a weekly digest instead of a per-release document.

Teams where the TSR is a formality. If nobody has vetoed a release because of a TSR in the last year, cut it down to the one-page Minto version or drop it. A ritual report is worse than none, because it creates the illusion of governance.

FAQ

What’s the difference between a test summary report and a test report?

“Test report” is an umbrella term for daily status, execution logs, defect lists and summary reports. A test summary report consolidates the data for one release and ends with a Go/No-Go verdict. It is the capstone of the other reports.

What is TSR in testing?

TSR stands for test summary report: the end-of-cycle document that summarises test scope, results against exit criteria, open risks and a Go/No-Go recommendation. ISTQB CTFL v4.0.1 and ISO/IEC/IEEE 29119-3:2021 call it a test completion report; some teams say test closure report.

What is test reporting in software testing?

Test reporting is the practice of turning test results into documents people act on: daily status, per-run execution reports, defect logs, release notes and the test summary report. Only the test summary report ends with a Go/No-Go decision for a release.

Do agile teams need a test summary report every sprint?

No. Sprint reviews and a live dashboard cover sprint-level status. Write a test summary report when a release candidate, an audit or a customer sign-off needs a decision; teams on weekly releases generate one per release from CI.

What should a performance test report executive summary include?

The verdict, the load profile tested, the SLO results (p95 latency, error rate, throughput) against target, the first bottleneck found, and the recommendation. Raw tool output and graphs go to the appendix.

Is there a test execution summary report template for automation runs?

Yes: one row per suite with total, passed, failed, blocked or skipped, flaky (quarantined) and duration. Keeping blocked and flaky tests out of the pass count is what makes the template trustworthy.

How long should a test summary report be?

One page for the executive version. Two to four pages including the IEEE 829 / ISO 29119-3 appendix for regulated releases. Everything beyond that lives as a link to a dashboard or artifact archive. If your TSR is 20 pages, nobody reads it.

What metrics must every TSR include?

At minimum: pass rate, defect density, defect removal efficiency (DRE), defect leakage ratio (DLR) on Sev-1/2, requirements coverage, automation flakiness, MTTR. Those seven plus a verdict cover most of what release gatekeepers need.

Who should write the test summary report?

The QA lead owns it. In 2026 the first draft is AI-generated from CI metadata and test management tools; the owner edits the risk and verdict paragraphs, then circulates it for sign-off. The QA lead’s name stays on the document.

How often should we produce a TSR?

Once per release candidate. Weekly releases produce weekly TSRs; monthly releases produce monthly. Continuous-deployment teams roll up into weekly or bi-weekly digests. The cadence tracks the decision the report supports.

Can AI write a test summary report?

AI tools (Momentic, QA Wolf, and in-house LLM pipelines) now draft the narrative from CI metadata and test tools in seconds. AI cannot accept residual risk on the business’s behalf, so that paragraph stays human. Typical time savings: 4–6 hours down to 30 minutes per release. Google’s 2025 DORA (DevOps Research and Assessment) report found 90% of software professionals use AI but only 24% trust it a lot or a great deal, which is why the verdict stays with a person.

What is Defect Removal Efficiency (DRE) and why does it matter?

DRE = defects found in testing divided by the sum of defects found in testing and defects found in production. Target above 90%. Track it quarter over quarter; a declining DRE is the earliest signal that test scope is drifting behind product scope.

How do we handle a release where exit criteria weren’t met?

Return a “No-Go” verdict with a concrete rationale: which criteria failed, which Sev-1/2 defects are unresolved, and the estimated delay to fix them. Follow up with a plan and a revised release date. Shipping over the team’s “No-Go” even once erodes trust in every later TSR, so don’t.

QA process

How we ensure quality testing at every stage of product development

The SDLC context your TSR sits inside.

Quality testing

How to test WebRTC stream quality in 2026

Vertical-specific metrics for your TSR’s streaming section.

AI in QA

AI in quality assurance: practical applications

How to automate the 80% of the TSR that doesn’t need a human.

Payments QA

How we ensure payment system reliability

Worked example of a TSR for a high-stakes vertical.

Reliability

How to build reliable, crash-proof software in 2026

SLOs, DORA metrics, and the patterns your TSR verifies.

Ready to ship a TSR the business actually reads?

A 2026-grade test summary report leads with a verdict, names the seven metrics that matter and fits on a single page, with everything else in linked appendices. If your current TSR is three pages of pass rates and nobody acts on it, it is ceremony rather than reporting.

Swap the ceremony for the Minto-pyramid template, automate the metrics collection out of CI, and leave the QA lead only the risk paragraph. TSR prep per release drops from four-to-six hours to thirty minutes. Escapes drop because the artifact enforces the exit criteria. Executives trust the verdict because the numbers always sit on the same seven axes.

Book cover: Video Streaming, Volume 3 of the Fora Soft Video Engineering HandbookBook cover: Video Encoding, Volume 1 of the Fora Soft Video Engineering HandbookBook cover: Audio for Video, Volume 5 of the Fora Soft Video Engineering Handbook

The handbook · 7 volumes

Fora Soft Video Engineering Handbook

A test report for a video product needs numbers for picture and sound, not only pass rates. We wrote seven volumes on the video stack, from encoding and delivery to sound and AI. QA leads can start with the encoding volume on video quality metrics, then add the audio volume on PESQ, POLQA and ViSQOL and the delivery volume on QoE monitoring. Written by Nikolay Sapunov, CEO at Fora Soft.

Browse the handbook on Amazon →7 volumes · 9,000+ pages · Kindle & paperback

Want the TSR template plus the CI automation in 3 weeks?

Fixed scope, fixed timeline. Minto-pyramid TSR, seven-metric dashboard, AI-drafted narrative, Jira + Slack delivery. Your QA lead edits the risk section and hits approve.

Book a 30-min call → WhatsApp → Email us →

  • Processes