Scheduling
Run Bug0 tests on a schedule to monitor your application continuously and catch issues before users report them.
Why Schedule Tests?
Scheduled tests help you:
- Monitor production - Catch issues in real-time
- Detect regressions - Find bugs that slip through
- Verify integrations - Ensure third-party services work
- Track reliability - Build a history of test results
How Scheduling Works
1. Create a schedule (hourly, daily, etc.)
2. Bug0 triggers tests automatically
3. Tests run against your specified URL
4. Results sent via configured notifications
Schedule Options
| Interval | Use Case |
|---|---|
| Every 15 minutes | Critical path monitoring |
| Hourly | Regular health checks |
| Daily | Comprehensive regression tests |
| Weekly | Full suite validation |
Creating a Schedule
See Creating Schedules for step-by-step instructions.
Notifications
Scheduled test results are sent via:
- Email - If email integration configured
- Slack - If Slack integration configured
Configure notifications in Project Settings → Integrations.
Schedule Management
View Schedules
Go to Project Settings → Schedules to see all schedules.
Pause a Schedule
- Find the schedule in settings
- Click Pause
- Schedule won't trigger until resumed
Resume a Schedule
- Find the paused schedule
- Click Resume
- Next run calculated from current time
Delete a Schedule
- Find the schedule
- Click Delete
- Confirm deletion
Best Practices
Choose Appropriate Frequency
- High-frequency (15 min) for critical flows only
- Hourly for important features
- Daily for full regression
Use Production URLs
Schedule against production to catch real issues.
Configure Notifications
Ensure you're notified of failures immediately.
Review Results Regularly
Don't just set and forget—review trends and patterns.