Scheduled Test Runs Are Here

People kept asking for this one. You can now schedule AI tests to run automatically - true test automation without the maintenance burden.

Why we built this

Running tests by hand works fine when you're actively hacking on something. But nobody wants to wake up at 2 AM to run regression tests. And you probably want to know if production broke before your users do.

With AI testing, you get intelligent test execution that adapts to your UI changes. With scheduled runs, you get hands-off test automation that keeps your app validated around the clock.

Some things that schedules are good for:

• Checking production health every few hours
• Running the full test suite overnight
• Smoke tests before your team starts work

Setting it up

Go to Schedules in your dashboard, create one, pick your test plans, and set a frequency. That's pretty much it.

We have presets for common stuff:

• Every 30 minutes
• Hourly
• Daily at 9 AM UTC
• Weekdays only

Or write your own cron expression if those don't work. Something like 0 6,18 * * 1-5 runs at 6 AM and 6 PM on weekdays.

Multiple test plans per schedule

You can group test plans together. A single schedule triggers all of them in parallel.

"Morning Check" schedule
├── Login Flow
├── Product Search  
└── Checkout

All three run at the same time when the schedule fires.

Pausing schedules

Need to stop a schedule temporarily? Toggle it off. Your config stays saved. Turn it back on whenever.

Useful when you're deploying something big or doing maintenance and don't want tests running in the middle of it.

Run Now button

If you don't want to wait for the next scheduled time, just hit Run Now. Good for testing that your schedule actually works, or when you just pushed a fix and want to check it.

How we use it

We run health checks on our demo site every 30 minutes. Full regression runs at 3 AM. Quick tests after deploys via the CI integration.

Between schedules and CI triggers, we've got most scenarios covered.

Webhooks still work

Scheduled tests trigger webhooks when they finish. Same format as everything else. Hook it up to Slack or whatever you use.

Credits

Same pricing as manual runs. Quick mode for the frequent stuff, Deep mode for thorough overnight runs. The dashboard shows cost per run so you know what to expect.

Why AI testing + schedules = better test automation

Traditional test automation breaks constantly. Selectors change, layouts shift, and suddenly your entire test suite is red. You spend more time fixing tests than writing features.

AI testing handles this differently. Our agents navigate your app like real users - they don't care if a button moved 10 pixels or got renamed. Combine that with scheduled runs, and you get:

• Zero-maintenance regression testing - AI adapts to UI changes automatically
• Continuous validation - Catch bugs before users report them
• Scalable test automation - Add coverage without adding maintenance burden

This is what modern test automation should look like: set it up once, let AI handle the execution, and get notified when something actually breaks.

Docs are at /docs/schedules if you want the full cron syntax reference.