Test-Lab.aiDocs

Schedules

Automate test execution with cron-based scheduling

Schedules

Schedules let you run test plans automatically at specified intervals. Perfect for continuous monitoring, nightly regression tests, or hourly smoke tests.

Creating a Schedule

  1. Go to DashboardSchedules
  2. Click Create Schedule
  3. Configure the schedule:
FieldDescription
NameDescriptive name (e.g., "Nightly Regression")
Test PlansSelect one or more test plans to run
FrequencyChoose a preset or custom cron expression
Test TypeQuick or Deep mode
EnabledToggle to activate/deactivate

Frequency Options

Presets

PresetCron ExpressionRuns At
Every 30 minutes0,30 * * * *:00 and :30 every hour
Hourly0 * * * *Top of every hour
Every 6 hours0 */6 * * *00:00, 06:00, 12:00, 18:00
Daily at 9am UTC0 9 * * *09:00 UTC daily
Weekdays at 8am UTC0 8 * * 1-508:00 UTC Mon-Fri
Weekly (Sunday)0 0 * * 000:00 UTC Sundays

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:

ExpressionDescription
0 */2 * * *Every 2 hours
30 9 * * 1-59:30 AM UTC, weekdays only
0 0 1 * *First day of each month
0 6,18 * * *6 AM and 6 PM UTC daily

All times are in UTC. Convert to your local timezone when setting up schedules.

Multiple Test Plans

A single schedule can run multiple test plans. All selected plans execute in parallel when the schedule triggers.

Schedule: "Morning Smoke Tests"
├── Login Flow Test
├── Homepage Test
└── Checkout Test

Schedule Management

Enable/Disable

Toggle schedules on or off without deleting them. Useful for:

  • Temporarily pausing during maintenance
  • Disabling during deployments
  • Testing schedule configuration

Manual Trigger

Run a schedule immediately without waiting for the next scheduled time:

  1. Find the schedule
  2. Click Run Now

Tracking

Each schedule shows:

  • Last Run - When it last executed
  • Next Run - Upcoming execution time
  • Test Plan Count - Number of plans in the schedule

Common Patterns

Continuous Monitoring

Name: Production Health Check
Frequency: Every 30 minutes
Test Plans: Critical path smoke test
Test Type: Quick

Nightly Regression

Name: Full Regression Suite
Frequency: Daily at 2 AM UTC
Test Plans: All regression tests
Test Type: Deep

Pre-Work Verification

Name: Morning Readiness Check
Frequency: Weekdays at 7 AM UTC
Test Plans: Key user journeys
Test Type: Quick

Webhook Integration

When a scheduled test completes, webhooks are triggered for each test plan's project. Configure webhooks in your project settings.

Credit Usage

Scheduled runs consume credits like manual runs:

  • Quick tests: Standard rate
  • Deep tests: Higher rate

Use Quick mode for frequent schedules and Deep mode for less frequent, thorough checks.

Next Steps

On this page