Know your critical tests still work, every hour, every day.

A smoke test is a quick check of the most important paths through your app, the journeys that, if broken, mean the product is effectively down. For a web app that usually means sign-up, login, checkout, and core onboarding. If those pass, the build is healthy enough to trust.

A scheduled smoke test re-runs those critical tests automatically on a set cadence, hourly, daily, or weekly, instead of only when you deploy. It is continuous monitoring for the journeys users actually take, and it catches breakage that appears between releases, like an expired token, a third-party outage, or a config change, before users report it.

Run the tests that make you money as often as they change or as often as a quiet failure would hurt. Many teams run checkout and login hourly or a few times a day, and broader journeys daily. You can set a different cadence per test.

Smoketest uses timezone-aware presets: run a test every few hours, at chosen times each day, or on a specific day each week. Pick the cadence per test from your project settings, no cron syntax to write.

Post-deploy testing runs when you ship; scheduled smoke tests run on the clock. Together they cover both kinds of breakage, the change you just made, and the failure that creeps in between deploys. Most teams use both on the same tests.

Yes. Send notifications to email, Slack, or Discord, and filter them per project: every run, or failures and recovery only so you hear when a test breaks and when it comes back, without a ping on every green run. You hear about a broken test before your customers do.

Yes. Store a test account and card as environment variables and the agent logs in and completes the purchase on each scheduled run. Secrets stay out of your test text and out of the logs.

No. Uptime checks confirm a page responds. A scheduled smoke test drives the real user journey in a real browser, clicking, typing, and verifying the outcome, so it catches a broken checkout that still returns 200 OK.

Yes. Each run uses one credit for up to ten minutes of run time. The plan includes 300 credits a month, and you can add more if your cadence needs them.

Write a test in a sentence, run it once to confirm it does what you mean, then pick a schedule from the test's settings. From then on it runs on its own and alerts you if it breaks.