Creating Schedules
Set up automated test runs on a recurring schedule.
Creating a Schedule
- Open your project
- Go to Project Settings then Schedules
- Click Create Schedule
- Configure the schedule:
| Field | Description |
|---|---|
| Suite | Which suite to run (or "All Suites") |
| Interval | How often to run (15 min, hourly, daily, weekly) |
| Base URL | URL to test (optional, uses project URL if empty) |
| Timezone | Your timezone for daily/weekly schedules |
- Click Create
Schedule Configuration
Suite Selection
All Suites:
- Runs all active test suites in order
- Login then Regular then Cleanup
Specific Suite:
- Runs only the selected suite
- Useful for targeted monitoring
Interval Options
| Interval | Runs At |
|---|---|
| Every 15 minutes | :00, :15, :30, :45 |
| Hourly | Top of each hour |
| Daily | Configured time in your timezone |
| Weekly | Configured day and time |
Base URL Override
Leave empty to use the project's base URL, or specify a different URL:
https://www.yourapp.com (production)
https://staging.yourapp.com (staging)
Use different schedules for different environments - one for production monitoring, another for staging validation.
Managing Schedules
View All Schedules
Go to Project Settings then Schedules to see:
- Schedule name/description
- Interval and next run time
- Status (active/paused)
- Last run result
Edit a Schedule
- Click on the schedule
- Modify settings
- Save changes
Changes take effect on the next run.
Pause/Resume
Toggle the schedule status:
- Pause - Stop automatic runs
- Resume - Continue automatic runs
Delete a Schedule
- Click Delete on the schedule
- Confirm deletion
- Schedule is permanently removed
Example Schedules
Production Monitoring
Suite: Critical Paths
Interval: Every 15 minutes
URL: https://www.yourapp.com
Monitors login, checkout, and key flows continuously.
Daily Regression
Suite: All Suites
Interval: Daily at 6:00 AM
URL: https://www.yourapp.com
Runs full test suite every morning.
Weekly Full Suite
Suite: All Suites
Interval: Weekly on Sunday at 2:00 AM
URL: https://www.yourapp.com
Comprehensive weekly validation.
Notifications
Configure how you are notified of results:
Email Notifications
- Go to Project Settings then Integrations then Email
- Add recipient email addresses
- Choose when to notify (always, failures only)
Slack Notifications
- Go to Project Settings then Integrations then Slack
- Connect your Slack workspace
- Select notification channel
- Choose notification preferences
Viewing Schedule History
From Project Settings
- Go to Schedules
- Click on a schedule
- View run history with:
- Start/end times
- Pass/fail status
- Report links
From Execution History
- Go to project dashboard
- View Execution History
- Filter by "Scheduled" trigger type
Troubleshooting
Schedule Not Running
- Verify schedule is not paused
- Check schedule configuration
- Ensure project is active
Runs Failing Consistently
- Review test reports for errors
- Check if URL is accessible
- Verify credentials are still valid
Missing Notifications
- Verify integration is configured
- Check notification preferences
- Look in spam/junk folders
Best Practices
Start with Lower Frequency
Begin with daily schedules, increase frequency as needed.
Monitor Critical Paths
Prioritize high-frequency schedules for:
- Login flows
- Payment processing
- Core functionality
Rotate Test Data
Use dynamic placeholders to avoid data conflicts:
{{run.email}}generates unique email per test{{run.shortid}}generates unique ID per test
Review Failures Promptly
Set up immediate notifications for failures and investigate quickly.