Scheduling Automated Tests
Set up automated test schedules to run tests on a recurring basis for continuous monitoring.
Scheduling Tests
Automate your testing workflow by scheduling test suites to run at specific times. This ensures your website is continuously monitored without manual intervention.
Accessing Schedules
Navigate to Schedules in the sidebar, or use the Schedules quick action on your Dashboard.
Creating a Schedule
Click the + New Schedule button.
Choose which test suite to run on schedule.
Select from available presets or create a custom cron expression.
Choose your preferred timezone for the schedule.
Toggle the schedule on and save.
Schedule Presets
AegisRunner offers common schedule presets:
| Preset | Description | Cron Expression |
|---|---|---|
| Every hour | Runs at the start of every hour | 0 * * * * |
| Every 6 hours | Runs 4 times per day | 0 */6 * * * |
| Daily at midnight | Runs once daily at 12:00 AM | 0 0 * * * |
| Daily at 9am | Runs once daily at 9:00 AM | 0 9 * * * |
| Weekdays at 9am | Runs Monday-Friday at 9:00 AM | 0 9 * * 1-5 |
| Every Monday | Runs weekly on Mondays at midnight | 0 0 * * 1 |
| Monthly | Runs on the 1st of each month | 0 0 1 * * |
Custom Cron Expressions
For advanced scheduling, use custom cron expressions:
┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday = 0)
│ │ │ │ │
* * * * *
Examples
| Expression | Meaning |
|---|---|
0 */2 * * * |
Every 2 hours |
30 9 * * 1-5 |
9:30 AM on weekdays |
0 6,18 * * * |
6 AM and 6 PM daily |
0 0 * * 0 |
Every Sunday at midnight |
0 9 1,15 * * |
1st and 15th of each month at 9 AM |
Timezone Configuration
Schedules run in your configured timezone. Choose from all IANA timezone identifiers:
- America/New_York (EST/EDT)
- America/Los_Angeles (PST/PDT)
- Europe/London (GMT/BST)
- Asia/Tokyo (JST)
- Asia/Kolkata (IST)
- And many more...
Managing Schedules
View All Schedules
The Schedules page shows all configured schedules with:
- Test suite name
- Schedule frequency
- Next run time
- Last run status
- Enable/disable toggle
Enable/Disable
Toggle schedules on or off without deleting them. Disabled schedules won't run but retain their configuration.
Run Now
Click Run Now to execute the scheduled test immediately, outside of the regular schedule.
Edit Schedule
Modify the test suite, timing, or timezone of an existing schedule.
Delete Schedule
Remove a schedule permanently. This doesn't affect the test suite itself.
Scheduled Run Notifications
Receive notifications when scheduled runs complete:
- Email - Get notified of failures via email
- Slack - Send results to Slack channels (with integration)
Common Scheduling Strategies
Smoke Tests
Run critical tests frequently:
- Every hour or every 2 hours
- Catches issues quickly
- Use a composite suite with key tests
Regression Tests
Run comprehensive tests less frequently:
- Daily at night (minimal traffic)
- Full test suite coverage
- Review results each morning
Post-Deployment Tests
Trigger tests after deployments:
- Use the API to trigger runs
- Or schedule shortly after deploy windows
Best Practices
- Schedule resource-intensive tests during off-peak hours
- Stagger multiple schedules to avoid overlapping runs
- Use "Daily at 9am" for tests you want to review at work start
- Create separate schedules for different browsers
- Monitor schedule performance and adjust frequency as needed
- Keep smoke tests fast for frequent runs
Monitoring Scheduled Runs
Track scheduled run performance:
- Dashboard - Recent runs section shows scheduled runs
- Test Runs - Filter to see all runs including scheduled
- Usage - Monitor how schedules affect your run quota
Related Documentation
- Running Tests - Understand test execution
- Composite Test Suites - Create suites for scheduling
- CI/CD Integration - Trigger tests from pipelines
- Slack Integration - Get notifications in Slack