Test Execution Time Calculator
Estimate total test suite execution time given test count and parallel workers.
About Test Execution Time Calculator
Test suite execution time scales down roughly linearly with parallelism — splitting tests across more workers divides the base execution time — but flaky tests that fail and get retried effectively run twice, adding overhead proportional to the flaky rate. Modeling that overhead separately makes clear that flaky tests cost real pipeline time even when they eventually pass, which is often an underappreciated tax on CI throughput distinct from genuine test failures.
Formula
totalTime = (tests / parallelism × avgDuration) + (tests × flakyRate / parallelism × avgDuration)
- N
- Total tests
- t
- Average test duration in ms
- f
- Flaky test rate (as decimal)
- P
- Parallelism (workers)
- T
- Total execution time in ms
Worked example
With the default values below, Test Execution Time Calculator returns Total Test Execution Time of 37.08. Change any input above and every figure here is recalculated in your browser.
Inputs used
- Total Testsaccepts 1–10,000,000 tests
- 2,400 tests
- Parallelismaccepts 1–10,000 workers
- 8 workers
- Average Test Durationaccepts 0.1–3,600,000 ms
- 120 ms
- Flaky Test Rateaccepts 0–100
- 3
Results
- Total Test Execution Time
- 37.08 sec
- Base Execution Time
- 36,000.0 ms
- Flaky Retry Overhead Share
- 2.9%
Step by step
- 1Base time = (tests ÷ parallelism) × avg duration= 36000.0ms
- 2Flaky retry overhead= 1080.0ms
- 3Total time = base + flaky overhead= 37080.0ms (37.08s)
Assumptions and limits
- The result is derived only from the 4 inputs listed above. Anything not among them is not part of the calculation.
- In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
- Figures are rounded for display to 2 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.
How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.
Frequently Asked Questions
Does parallelism reduce flaky test overhead too?
Yes — retries of flaky tests are typically distributed across the same parallel workers as the initial run, so the flaky overhead is also divided by the parallelism factor in this model, though in practice retry scheduling can add extra coordination delay not captured here.
What flaky test rate is considered acceptable?
Best-in-class suites keep flaky rates under 1%; rates above 3–5% meaningfully inflate CI time and erode trust in the suite, often signalling shared test state, timing assumptions, or external service dependencies that need fixing rather than just retrying around.
Is retrying flaky tests once always sufficient?
Not necessarily — some CI systems retry failed tests multiple times before marking the suite as failed; each additional retry attempt compounds the overhead this calculator estimates, so suites with aggressive multi-retry policies should scale the flaky overhead accordingly.