Schedule Runs

Create scheduled TestVibe runs for recurring smoke checks, regression passes, and environment monitoring.

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. Select + (New automation) and enter a name.

3. For Trigger mode, choose Time (cron) and pick a schedule preset and timezone.

4. Set the Run Settings — site URL, the groups or tests to include, and one or more run configurations.

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.

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 all groups or a selected subset. If no group is selected, TestVibe treats the schedule as an all-groups run.

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

Use Run now to start the schedule 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

Scheduled runs are designed to avoid overlapping work. If a previous scheduled run is still active, the next scheduled attempt may be skipped instead of starting another copy of the same run.

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