Scheduled Checks
Scheduled checks allow you to run your test suites automatically at regular intervals. This helps you monitor your application continuously and catch issues before they impact users.
Overview
With Stably’s scheduled checks, you can:- Write high-level test prompts (e.g. “Verify all pages on the marketing page are working”)
- Run test suites on a recurring schedule (e.g. every day at 10am)
- Get notifications when tests fail
- Monitor critical user journeys automatically
Setting Up Scheduled Tests
Setting Up Scheduled Tests
Creating a Schedule
To create a scheduled test:- Navigate to Run Tests > Schedule Tests
- Click Create Schedule or similar option
- Configure your schedule settings:
- Days: Select which days of the week to run tests
- Times: Choose specific times to execute tests
- Timezone: Set the timezone for your schedule
- Configure notifications, retries, and other test execution settings
- These settings apply to all test runs (API, GitHub, and Scheduled triggers)
- Click Open Suite Settings to modify these configurations
- Click Save to create your schedule
Schedule Options
Schedule Options
Days Selection:
- Choose specific days of the week
- Options include individual weekdays, weekends, or daily execution
- Set specific times when tests should run
- Multiple time slots can be configured for more frequent execution
- Configure schedules in your local timezone
- Ensures tests run at the expected times for your team
Test Execution
Test Execution
When scheduled tests run:
- The selected test suite executes automatically
- All configured suite settings are applied
- Results are available in your test dashboard
- Notifications are sent based on your suite settings
Notifications and Monitoring
Notifications and Monitoring
Alert Configuration:
- Set up notifications through your suite settings
- Configure who receives alerts when tests fail
- Customize notification preferences for different scenarios
- View scheduled test results in your dashboard
- Track test success/failure trends over time
- Access detailed logs and screenshots for failed tests
Best Practices
Best Practices
Schedule Planning:
- Consider your application’s usage patterns when setting schedules
- Run critical tests more frequently during business hours
- Balance monitoring needs with resource usage
- Focus on your most important user journeys
- Include tests that validate critical functionality
- Keep test suites focused and reliable
- Configure appropriate notification settings
- Ensure the right team members receive alerts
- Test your notification setup to verify it works
Related Features
- Run Configuration - Test execution settings
- Alerting - Notification configuration
- CI Integration - Automated testing in CI/CD pipelines