Run tests on a schedule
Schedules let Qodex run scenarios automatically. Use them for nightly regression, hourly smoke checks, security sweeps, or recurring validation against a staging or production environment. A schedule stores the run scope, environment, cron expression, timezone, and notification settings. When the schedule fires, Qodex creates a normal test run and records results in the same history as manual runs.What a schedule controls
Each schedule defines:- Run scope: all active scenarios, a tag-filtered set, or selected scenarios and groups.
- Environment: the target environment for base URLs, credentials, and variables.
- Cron expression: when the run should fire.
- Timezone: how the cron expression should be interpreted.
- Notifications: who should be notified and when.
Create a schedule
Open Schedules, then click Create schedule. Name the schedule, choose the environment, and choose what should run.
Scenario groups run as one unit. Sequential groups run members in order and can stop on first failure. Parallel groups run members independently at the same time. See Test groups and folders for the full behavior.
Choose the cadence
Qodex uses standard five-field cron syntax.Pause, resume, or run now
Use the schedule’s Active toggle to pause or resume recurring execution. Pausing keeps the schedule definition intact. If you want CI to fire a paused schedule on demand, use the schedule’s webhook URL. The webhook can trigger the same run without enabling the cron schedule or shifting the next scheduled slot.Notifications
Schedules can notify on failure, always, or never. Completion payloads include the final result, scenario counts, and a link to the run detail page.Related
Run tests via webhook
Trigger a schedule or run from an external system.
Run the full suite
Understand the scope used by nightly regressions.
Test groups and folders
Learn how grouped scenarios run on schedules.