Understanding Test Execution Progress
How we calculate. Progress % = (executed ÷ planned) × 100 for one test cycle. The form uses the same arithmetic as the worked examples on this page. See our methodology and accuracy policy.
Real-world scenario: A typical Test Execution Progress case uses executed tests 320 and planned tests 400. Enter the same figures below to reproduce the worked path.
What is Test Execution Progress?
This is a schedule/completeness metric for test runs. Pair it with pass rate and fail rate to judge quality, not just throughput.
- Executed usually means run to a final status (pass, fail, blocked)
- Planned is the agreed suite size for the cycle
- Blocked tests often still count as executed if they consumed a run attempt—document your rule
The Formula
Worked Example
Common Use Cases
- Daily standups: report suite completion
- Release readiness: see remaining execution volume
- Capacity planning: compare progress vs calendar burn
Pro Tips
- Do not confuse with pass rate — 100% progress can still have many fails
- Re-baselines: if planned count changes mid-cycle, note the change date
- Track blocked separately when environment issues stall runs
Limitations: Test Execution Progress results are estimates for learning and QA planning—not contractual SLAs. Align definitions with your org’s quality glossary before executive reporting.
FAQ
Should retests count again?
For cycle progress, count unique planned cases once unless your process tracks retest waves separately.
What about automation that runs nightly?
Use the planned suite size for the release gate, not every CI repeat, unless you are measuring CI throughput specifically.
Authoritative References
For software quality metrics definitions, consult established engineering sources:
- ISTQB — software testing glossary and practices
- ISO/IEC 25010 — systems and software quality models
- IEEE — software engineering standards