Regression testing that grows with every ticket
Automated regression testing re-runs your checks after each change, to catch what used to work and no longer does. With Smoketest, a ticket that passes can become a lasting check, so your coverage grows as you ship.
How your coverage grows
It builds from the work your team is already doing, one ticket at a time.
- 1
A ticket passes
It tests the ticket as it reaches QA and leaves the proof there.
- 2
It becomes a check
Save the ones that matter, and they join your regression set.
- 3
It runs when you say
After each deploy, on pull requests, or on a schedule.
- 4
You hear when it breaks
You get an alert when a check fails, and another when it recovers.
Three ways to run regression
Each one runs your checks automatically. The difference is who keeps them going.
| Scripted suite | Managed suite | Smoketest | |
|---|---|---|---|
| Who writes the checks | Scripted suiteYour engineers | Managed suiteThe vendor's team | SmoketestIt does, from each ticket |
| How coverage grows | Scripted suiteSomeone writes another test | Managed suiteThe vendor adds flows to the plan | SmoketestWith each ticket that passes |
| When a screen changes | Scripted suiteSomeone fixes the test | Managed suiteThe vendor fixes it | SmoketestIt follows the goal |
| When it runs | Scripted suiteOn each build | Managed suiteOn each pull request or release | SmoketestOn deploys, pull requests, or a schedule |
| What a failure gives you | Scripted suiteA log and a stack trace | Managed suiteA bug report | SmoketestResult, recording, and steps |
| What it costs | Scripted suiteYour team's time | Managed suiteFrom $2,500 a month | SmoketestFrom $399 a month for 1,000 runs |
When each one fits
Plenty of teams run more than one. Here is how we would decide.
A scripted suite fits when
- Your engineers want tests next to their code
- A few flows need the same exact check
- Someone has time to look after the suite
A managed suite fits when
- You want a vendor to own the whole suite
- You want a person checking each failure
- You have a budget for a monthly contract
Smoketest fits when
- You have no regression suite yet
- Your coverage should follow what you ship
- You want one teammate for tickets and regression
What it costs
A person running regression by hand costs the most, and it is usually the first thing cut when the sprint runs out. Automated checks cost the same on the busiest week.
Market ranges from BLS, May 2025, Bug0, and Vendr. Your quote will vary.
Failed · 3 of 4 saved checks · 4m 18s · After deploy
- ✓Admin can add a seat
- ✓Invoice preview shows the proration
- ✓A customer can update their card
- ✗A coupon applies at checkout
Not tested: annual plans, because no saved check covers them yet.
Watch the recording · View attempt
That came in with this morning's deploy. Rolling it back.
Here is a regression run after a deploy.
It started as a real ticket
Each saved check came from work you shipped, so it tests what matters.
It runs without anyone asking
A deploy, a pull request, or a schedule can start it.
You hear about it twice
You get one alert when it breaks, and another when it recovers.
Questions about automated regression testing
Weighing other options? See them side by side
It means re-running your checks automatically after each change, to catch anything that used to work and no longer does. A person no longer has to walk through the same flows by hand.
A smoke test is a short check that the main flows still work. A regression set is wider and covers everything you have saved. Most teams run smoke tests on each deploy and the full set less often.
Yes. A deployment or a pull request check can start your saved checks, so you know within minutes whether a release broke something.
Yes. Run saved checks hourly, daily, or weekly. Point one at production and it works as a monitor too, with an alert when it breaks or recovers.
No. Each one starts as a ticket it has already tested. You choose which ones to keep, and you can edit them.
Yes. Keep what works. Smoketest adds checks for the new work on each ticket, where nobody has written a test yet.
It starts at $399 a month for 1,000 runs. Each run is up to 10 minutes, and a longer test counts as two runs or more, one for every 10 minutes. If your team needs more, we design a Scale plan with you, so you stop buying extra runs.
Every result links to the recording, the steps, and the reasoning, and says what it did not test, so you can check its work the way you would check a teammate's.
Turn your next ticket into a lasting check.
Book a call and we will test one with you. If it passes, it can join your regression set the same day.