Schedule Runs

Scheduled runs let TestVibe execute selected tests on a recurring cadence without starting each run manually.

Use schedules for smoke checks, overnight regression coverage, staging environment monitoring, or any test set that should run at a predictable time. Schedules are managed as Automations — the same surface can also trigger runs when another run finishes.

Create a scheduled run

1. Open Automations from the navigation rail.
2. Choose New automation → Run tests under In TestVibe, then enter a name.
3. Under Trigger, choose On a schedule, then set How often and Timezone.
4. Under Action, keep Run tests selected. Open Choose tests or Change to pick tests, then Done. Expand Advanced options to review the environment and configuration.
5. Leave Enabled on if the schedule should start running.
6. Save the automation.

TestVibe saves the automation to your project and starts a cloud test session automatically at each scheduled time.

For a schedule managed by GitHub Actions, use New automation → From GitHub → On a schedule instead. That template creates a daily UTC workflow through a setup pull request; it is separate from the TestVibe scheduler below. See GitHub workflows.

Frequency options

Pick a schedule preset, then choose a timezone:

Frequency	Use it for
Every 15 minutes	Fast feedback for highly active test environments.
Hourly	Frequent monitoring without running constantly.
Daily at 02:00	An overnight health check before the workday starts.
Daily at 09:00	A morning health check for the team.
Weekly (Mon 06:00)	Weekly regression checks at the start of the week.

Choose what the schedule runs

Schedules can target individual tests or folders. The picker summarizes an empty selection as All runnable tests; review that summary before saving a full-suite schedule.

Choose the smallest useful scope:

Scope	Best for
One group	Monitoring a critical workflow such as sign-in or checkout.
Several groups	Daily confidence for the main product paths.
Full suite	Broad regression coverage on a slower cadence.

Site URL source

A schedule can use:

Source	When to use it
Explicit URL	The schedule should always run against a specific environment.
Project site URL	The project already defines the correct app URL.

Use explicit URLs for staging, QA, preview, or dedicated test environments.

Run now

Open the saved automation's … menu and choose Run now to start it immediately without waiting for the next planned time. This is useful after creating or editing a schedule because it confirms the selected tests, URL, and configuration work together.

Active-run behavior

Check the automation's history when an expected run does not appear. A disabled automation, unavailable target, dispatch failure, or concurrency protection may prevent a scheduled action from producing a run; do not infer success from the scheduled time alone.

For execution environment options, including tunnel devices for private apps, see Choose a runner.