What Is a Test Execution Report?
A test execution report summarizes the results of running test cases against a specific build or release. It answers the critical question: “How is the quality of this build?”
Stakeholders — project managers, product owners, developers, executives — rely on these reports to make go/no-go decisions about releases.
Report Components
Execution Summary
| Metric | Value | Target |
|---|---|---|
| Total Test Cases | 450 | — |
| Executed | 420 (93%) | 100% |
| Passed | 385 (92%) | > 95% |
| Failed | 25 (6%) | < 5% |
| Blocked | 10 (2%) | 0% |
| Not Run | 30 (7%) | 0% |
Key Metrics
Pass Rate: (Passed / Executed) x 100
- Example: 385 / 420 = 91.7%
- Target: > 95% for release readiness
Execution Progress: (Executed / Total) x 100
- Example: 420 / 450 = 93.3%
- Shows how much testing is complete
Defect Density: Defects found / Features tested
- Example: 25 defects / 12 features = 2.08 defects per feature
- High density areas need more attention
Defect Detection Rate: Defects found in testing / Total defects (testing + production)
- Measures testing effectiveness
- Target: > 90% (find 90% of bugs before production)
Defect Summary
| Severity | Open | Fixed | Verified | Total |
|---|---|---|---|---|
| Critical | 0 | 2 | 2 | 4 |
| Major | 3 | 8 | 5 | 16 |
| Minor | 5 | 12 | 10 | 27 |
| Trivial | 2 | 3 | 3 | 8 |
| Total | 10 | 25 | 20 | 55 |
Test Results by Feature
| Feature | Total | Passed | Failed | Blocked | Pass Rate |
|---|---|---|---|---|---|
| Authentication | 45 | 42 | 2 | 1 | 95.5% |
| Payment | 60 | 50 | 8 | 2 | 86.2% |
| Search | 35 | 34 | 1 | 0 | 97.1% |
| User Profile | 25 | 24 | 1 | 0 | 96.0% |
| Notifications | 20 | 15 | 3 | 2 | 83.3% |
Trends
Show progress over time:
- Daily pass rate trend (should increase as bugs are fixed)
- Cumulative test execution (should reach 100% before release)
- Open defects trend (should decrease as bugs are fixed)
Report Audiences
Different stakeholders need different levels of detail:
| Audience | Needs | Format |
|---|---|---|
| Executive | Go/no-go decision, risk summary | 1-page summary, traffic lights |
| Project Manager | Progress, blockers, schedule risk | Full report with trends |
| Development Lead | Which areas are failing, defect details | Detailed by component |
| QA Team | What to test next, blocked items | Execution status board |
Automation
Generating Reports Automatically
Most test management tools auto-generate reports:
- Zephyr Scale — built-in reports in Jira
- TestRail — milestone reports, comparison reports
- Xray — Jira dashboards and custom reports
- Allure — beautiful reports from automated test frameworks
CI/CD Integration
Automated test results from CI/CD pipelines should feed directly into execution reports. Tools like Allure, ReportPortal, and TestRail API integrations enable this.
Exercise: Create a Test Execution Report
Given this data, create a test execution report with recommendations:
- Build: v3.5.0-rc1
- Total test cases: 300
- Results: 250 passed, 30 failed, 10 blocked, 10 not run
- Critical bugs: 1 open (payment calculation error), 2 fixed
- Major bugs: 5 open, 8 fixed
- The payment module has 60% pass rate
- Release deadline: 3 days away
Solution
Executive Summary: Build v3.5.0-rc1 is NOT ready for release. Pass rate is 89.3% (target: 95%). One critical bug remains in payment calculations. The payment module needs significant attention at 60% pass rate.
Recommendation: Do NOT release. Fix critical payment bug, re-test payment module, address blocked tests. Re-evaluate in 2 days.
Risk Assessment:
- HIGH: Payment calculation error — potential financial loss, customer trust damage
- MEDIUM: 5 open major bugs — user experience degradation
- LOW: 10 blocked tests — likely environment issues, not product defects
Action Items:
- Fix critical payment bug immediately (Priority: P1)
- Investigate and resolve blocked tests (10 tests)
- Execute remaining 10 un-run tests
- Re-test all 30 failed tests after fixes
- Schedule regression run 1 day before deadline
Key Takeaways
- Test execution reports communicate quality status and enable release decisions
- Key metrics: pass rate, execution progress, defect density, and defect detection rate
- Tailor report detail to your audience: executives need summaries, developers need details
- Show trends over time — single snapshots do not tell the full story
- Automate report generation from test management tools and CI/CD pipelines
- Always include recommendations and risk assessment, not just raw numbers