Skip to content
OttoTester docs

Schedule recurring runs

What a schedule does

Section titled “What a schedule does”

A scheduled run runs a variant’s tests automatically, on a cadence. It’s how you turn OttoTester from something you click into a standing safety net — a smoke check every morning, a full regression every weekend.

A schedule pairs a variant with a template (the run configuration). When it fires, it produces an ordinary run and report — the same as if you’d started it by hand.

1. Create the schedule

Section titled “1. Create the schedule”

From the variant, create a scheduled run. You choose:

  • The template — which configuration to run.
  • Frequency — once, daily, weekly, or a custom cron expression for anything else (every six hours, weekday mornings only, and so on).
  • Time zone — so “9am daily” means 9am where your team is, not in UTC.
  • A start date, and optionally an end date.

2. Notifications on failure

Section titled “2. Notifications on failure”

A schedule is only useful if someone hears about a failure. OttoTester sends a notification when a scheduled run regresses — a test that was green is now failing — and when the schedule itself fails to dispatch. Who gets told, and whether by in-app notification or email, is set in each person’s notification preferences (Settings → Account → Notifications).

3. Pause and resume

Section titled “3. Pause and resume”

A schedule is either active or paused. Pause one before a known maintenance window so you don’t get noise, and resume it after. Pausing deletes nothing — the schedule keeps its configuration and its history.

Each schedule records its last run and its next run, so you can see at a glance when it last fired and when it will fire again.

Section titled “Related”