Skip to main content
Set up tests to run automatically without manual intervention.

​
Why Schedule Tests?

Scheduled tests help you:
  • Catch regressions early, before they reach production
  • Monitor critical user journeys continuously
  • Run tests during off-peak hours
  • Ensure consistent test coverage without manual execution

​
Creating a Schedule

Navigate to Schedules → New Schedule
1

Name your schedule

Give it a descriptive name like “Nightly Smoke Tests” or “Weekly Regression”
Use names that indicate both what runs and when (e.g., “Daily Checkout Tests - 2AM”)
2

Choose what to run

Select the scope of your schedule:
  • All Tests - Run every enabled test
  • Suite - Run all tests in a suite
  • Individual Test - Run a single test
3

Set frequency

Choose how often the schedule runs:
  • Daily
  • Weekly
  • Monthly
Runs every day at a specific timeBest for: Smoke tests, critical path validation
4

Choose time and timezone

Set the exact time for execution and your timezone.
Timezone matters! Ensure you select the correct timezone, especially for distributed teams.
5

Save and activate

Click Create Schedule - it’s active immediately and will run at the next scheduled time.

​
Managing Schedules

The Schedules page displays:
  • Schedule name and description
  • What it runs (suite/test name or “All Tests”)
  • Frequency and time
  • Status (Active or Paused)
  • Next scheduled run time

​
Pause/Resume

Click the pause icon to temporarily disable a schedule without deleting it. Click play to resume.
Paused schedules won’t execute until you resume them. This is useful for temporarily disabling tests during maintenance or known issues.

​
Edit Schedule

Click any schedule to modify:
  • Execution time
  • Frequency
  • What tests to run
  • Timezone
Changes take effect immediately and apply to the next scheduled run.

​
Delete Schedule

Click the delete icon to permanently remove a schedule. This doesn’t delete the tests themselves, only the schedule.

​
Troubleshooting

Check:
  • Schedule is active (not paused)
  • Timezone is correct
  • Tests in schedule are enabled
  • No system maintenance at scheduled time
Possible causes:
  • Application was down during execution
  • Browser profiles expired
  • Environment changes (URLs, credentials)
  • Network issues
Check test run details for specific errors.
Verify:
  • Timezone setting is correct
  • Your local time vs schedule timezone
  • Daylight saving time transitions