Scheduled Regression Testing & Automated Monitoring
Scheduled Automation allows you to run test cases or full Test Campaigns automatically at predefined times. Instead of relying on someone to remember to execute tests, the system handles it on a consistent schedule.
Why it matters
- Ensures regular regression coverage.
- Reduces human error or forgotten test runs.
- Provides consistent monitoring of system stability.
- Supports continuous testing workflows.
When to use it
- You want nightly regression runs.
- You need weekly stability checks.
- You run health checks after recurring deployments.
- You want automated monitoring during off-hours.
Core concepts
- Schedule – The predefined time and frequency for execution.
- Recurring Run – Repeated execution based on daily, weekly, or custom intervals.
- Time Zone Awareness – Execution respects the configured system time zone.
- Execution Log – Each scheduled run is recorded for traceability.
How it works
- You create a scheduled automation rule.
- You define the frequency (daily, weekly, or custom).
- The system tracks the schedule in the background.
- At the defined time, execution starts automatically.
- Results are stored and visible in the execution history.
How to use it
Step 1: Select target
Choose the test case or Test Campaign you want to schedule.
Step 2: Define frequency
Set how often the automation should run:
DailyWeeklyCustom interval
Step 3: Confirm time settings
Make sure the scheduled time aligns with your team’s time zone and deployment cycle.
Step 4: Activate and monitor
Enable the rule and monitor early runs to confirm correct behavior.
Best practices
- Schedule runs during low-traffic hours when possible.
- Keep regression suites optimized to avoid long execution times.
- Review schedule after major release timeline changes.
- Disable schedules temporarily during major infrastructure changes.
Common mistakes
❌ Scheduling unstable or incomplete test cases
✔ Stabilize workflows before enabling recurring execution.
❌ Forgetting to adjust schedules after environment changes
✔ Review timing after deployment process updates.
❌ Running heavy regression too frequently
✔ Balance coverage with system performance and cost.
Security & permissions
- Only authorized users can create or modify scheduled rules.
- Scheduled runs respect the same execution permissions as manual runs.
- All scheduled executions are logged for audit purposes.