Test automation ratio
The percentage of your test suite that runs without manual execution — a measure of scalable testing capacity.
// Formula
// About this metric
Test automation ratio measures what proportion of your test suite can be executed without a human tester performing steps manually. The formula is: automated tests divided by total tests (manual plus automated), expressed as a percentage.
A high automation ratio is generally desirable because automated tests can run on every commit, at any hour, without per-run labour cost. It enables continuous integration and fast feedback loops. However, the ratio itself can be misleading: 1,000 automated tests that test the wrong things at the wrong granularity may deliver less value than 100 automated tests at the right level plus 30 targeted manual test sessions.
The World Quality Report (2024–25) places the industry automation ratio at around 40–60% for most commercial software teams, with leading teams above 70%. The variation is significant because automation investment differs enormously by domain: consumer web applications have very different automation economics to embedded systems or native mobile apps.
The optimal automation mix follows the test pyramid: a large base of fast unit tests (almost all automated), a smaller layer of integration tests (largely automated), and a small number of E2E tests (automated for regression, manual for exploratory). Manual testing retains unique value for exploratory, usability, and session-based testing that automation cannot replicate.
// Calculator
🧮 Calculator
// Benchmark
Source: World Quality Report 2024-25
Higher isn't always better — manual exploratory testing catches things automation can't. Aim for 'automated where automation pays off', not 100%.
// When to use this metric
Use automation ratio to track whether your team's investment in automation is increasing its scalable testing capacity over time. Declining ratio in a growing product is a warning sign that test debt is accumulating.
Review it alongside automation maintenance cost: a high ratio built on brittle scripts that fail constantly is not a better outcome than a moderate ratio of reliable, well-maintained automated tests.
// Common pitfall
Higher isn't always better — manual exploratory testing catches things automation misses, and the "right" automation ratio depends on your domain, risk profile, and team structure. Teams chasing 100% automation often end up automating tests that shouldn't be automated — session-based exploratory, usability checks — while neglecting to make their automated tests actually useful. Aim for "automated where automation pays off", not 100%.