glossary · end-to-end testing

Tested pull request

what is tested pull request?

A tested pull request is one pull request on which at least one test ran, counted once however many times the suite ran on it. It is a billing unit rather than a technical one, and it exists so that re-running a suite after a fix costs nothing extra, which the common alternatives, credits and runner minutes, all quietly penalise.

Every meter teaches a behaviour. Credits and runner minutes teach you to run tests less often, because each run has a visible price attached. That is precisely backwards for end-to-end testing, where the only schedule that catches regressions is running on every change.

Per-seat pricing teaches a different bad habit, which is limiting who can see the results. Per-test pricing, where you pay for tests under management, teaches you to delete coverage when the bill grows.

Metering the pull request has its own bias, and it is worth stating: it favours teams that batch work into fewer, larger pull requests. That is a real trade-off, and it is the least harmful one available, because the thing it makes free is the thing you want people doing without hesitation.

in smolanalytics

The price is $19 a month with 100 tested pull requests included, then 10 cents each. Push a fix and run the suite again on the same pull request and it is still one unit. The 14-day trial runs at those limits with no card, and the agent runs on your own Anthropic key, so model calls are billed to you directly and never resold at a markup.

How it works shows where this fits in the loop, and the docs have the exact behaviour.

questions

What if I run the suite twenty times on one pull request?
It is one tested pull request. That is the entire point of the unit.
What happens past 100?
They are 10 cents each; nothing stops and nothing is dropped.

keep reading