Scheduled smoke tests

Hear about it before your customers do

A scheduled smoke test signs in and runs a real user flow on a timer, hourly, daily, or weekly, so you hear when it breaks. With Smoketest, a ticket that passed can keep running in production, with no test code to write.

Book a callTalk to our founder. You can start the same day.

How a tested ticket becomes a monitor

It is the last stage of the same test, so nobody writes anything twice.

  1. 1

    A ticket passes

    It tests the ticket as it reaches QA and leaves the proof there.

  2. 2

    You save it

    Keep the flows that matter, and they join your library.

  3. 3

    You pick a schedule

    Hourly, daily, or weekly, set for each test, in your timezone.

  4. 4

    You hear when it breaks

    You get an alert when a flow fails, and another when it recovers.

Three ways to watch a live product

Each one tells you something different, and plenty of teams run more than one.

Uptime checkScripted monitorSmoketest
What it checksUptime checkThat the page answersScripted monitorThe steps you codedSmoketestThe whole flow, signed in
Who writes itUptime checkNobody, you add a URLScripted monitorYour engineersSmoketestIt does, from the ticket
A checkout that loads but cannot payUptime checkLooks fineScripted monitorCaught, if someone wrote that checkSmoketestCaught
When a screen changesUptime checkNothing happensScripted monitorSomeone fixes the scriptSmoketestIt follows the goal
What a failure gives youUptime checkA status codeScripted monitorA log and a traceSmoketestResult, recording, and steps
How often it runsUptime checkEvery minute or soScripted monitorEvery few minutesSmoketestHourly, daily, or weekly

When each one fits

Here is how we would decide if we were in your seat.

An uptime check fits when

  • You want to know the site is up
  • You want a check every minute
  • You have a small budget

A scripted monitor fits when

  • Your engineers want monitors as code
  • You need frequent API checks
  • Someone has time to look after them

Smoketest fits when

  • A broken flow costs you money
  • Nobody has time to write monitors
  • You already test tickets with it

What each one costs

A broken checkout on a Saturday costs more than any of these. The real price of a monitor is who looks after it.

QA budget
C4fxFrom $399 a month for 1,000 runs
A
B
C
1
Option
Starts
Cost
2
Uptime check
Today
Free to a few dollars a month
3
Scripted monitor
Once it is written
From $24 a month, plus usage
4
Smoketest
Today
From $399 a month for 1,000 runs
Next yearHeadcount

Market ranges from Checkly's pricing. Your quote will vary.

Checkout, every hour
00:0023:00
  • Checkout failed17:02 · Pay button did nothing · 1m 48sWatch the recording
  • Checkout recovered18:02 · 4 of 4 checks passed

You hear about it once, with the proof.

Failures and recoveries

You get an alert when it breaks, and another when it is fixed.

The channel you pick

Email, Slack, or Discord, with each person choosing what they get.

A recording to open

You see the step that failed without running anything yourself.

Questions about scheduled smoke tests

Weighing other options? See them side by side

A short test of the flows that must work, such as signing in and paying, so you find a serious break early. A scheduled one runs on a timer, on production or on staging.

An uptime check asks whether the page answers. A smoke test signs in and works through the flow, so it catches the checkout that loads but cannot take a payment.

Hourly, daily, or weekly, set for each test, in your timezone.

Not everything breaks when you ship. An expired key, a changed partner API, or a full queue can break a flow on a quiet Sunday, and a schedule catches those.Read about regression testing.

Yes. Save a test account, and it signs in the way a person would, including email codes through its own inbox.

It only does what the test does, as the test account you give it. Keep a separate account for production, and point it at flows that are safe to repeat.

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.

Put your most important flow on a schedule.

Book a call and we will set one up with you. You see the first run and the recording the same day.

Ready for QA
Done
ACM-484
Run checkout every hour in production
Passed, recording