Most teams budget for the compute an end-to-end test uses and little else. Here are the unit economics of end-to-end testing at the smallest scale: one test, one month.
What one end-to-end test costs to own each month
Eight minutes to run, twice a day. What it costs you to own for a month:
- CI compute, 480 minutes at ~$0.01/min, $4.80
- Engineering, one hour. Writing it, fixing the flake, re-reading the failure that turned out to be a timing issue. At a loaded $100/hr, $100
- Tokens, if an agent authored it, $10
~$115 a month. For one test.
End-to-end test maintenance cost is most of the bill
Compute is 4% of that, and it’s the only line anyone optimizes. Shard the suite. Parallelize the runners. Shave the container spin-up. The other 96% is a person maintaining brittle selectors.
Engineering time alone is about 87% of the monthly figure, and most of it goes on maintaining those selectors and chasing flaky failures. That is why end-to-end test maintenance cost, not infrastructure, decides what a test really costs to own.
How to calculate the cost of one end-to-end test for your team
The cost of one end-to-end test comes from three inputs added together for each month:
- CI minutes multiplied by your cost per minute.
- Maintenance hours multiplied by your loaded hourly engineering rate.
- Token spend, if an AI agent authored the test.
In the example above that is 480 minutes at $0.01, one hour at $100 and $10 in tokens. Replace each figure with your own run time, run frequency, loaded rate and maintenance hours. Maintenance hours deserve the most care, because they include fixing flakes and investigating failures that turn out to be timing issues, not only repairing selectors. Multiply the result by the number of tests in your suite to see what end-to-end testing costs you each month.
Cost per maintained end-to-end test with Klarent
We charge somewhere between $8 and $20 per maintained test per month. No CI bill, it runs on our infrastructure. The price holds because of a purpose-built harness, and human reviewers who are trained to use that harness in the most effective way.
$20 versus $115.
Now look at which of those two numbers is larger. The review time costs more than the product. That’s the line I’d want a skeptic to sit with, because it means the remaining cost isn’t tooling, it’s attention, and there is no version of QA where you don’t pay that.
What a lower cost per test means for coverage
But the savings are the boring half of this.
At $115 a test, a hundred tests is $11.5k a month and you spend your planning meetings arguing about which hundred. At $18 all-in, that same budget holds six hundred.
That’s the number that matters. Not the discount. The coverage.
The three checkout variants. The flow only enterprise customers hit. The edge case that bit you in March and got a Jira ticket nobody picked up. None of it was blocked by budget. It was blocked by how much breakage your team could absorb in a sprint.
We price per maintained test because maintenance was the expensive part. Everything else was rounding.
