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.

Progress % = (executed ÷ planned) × 100 for one test cycle.

Tip: Keep “Executed Tests” and “Planned Tests” on the same basis (scope and counting rules) before you calculate.

Cluster: Software Testing hub · Professional KPIs · Percentage guide

Execution progress shows how far the team is through the planned test run—not whether those tests passed.

Enter executed tests and planned tests for the same cycle (sprint, regression pack, or release suite).

Tests run to a final status in this cycle
Total tests planned for the same cycle

Execution Progress %

Understanding Test Execution Progress

How we calculate. Progress % = (executed ÷ planned) × 100 for one test cycle. 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

Test Execution Progress
Progress % = (Executed tests ÷ Planned tests) × 100

Worked Example

Scenario: The regression pack has 400 planned cases. Testers have executed 320 so far.
Step 1: Executed = 320
Step 2: Planned = 400
Step 3: (320 ÷ 400) × 100 = 80%
Answer: Your score is 125% (verified with this calculator).

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
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

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.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

When to use this calculator

  • Use this page when your wording matches test execution progress and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about test execution progress? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this test execution progress calculator?

For test execution progress, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for test execution progress—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking test execution progress, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

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