Schedule recurring tests

A schedule turns a test into a regression check that runs without you. You set a cron expression and a timezone, and Maxoperf starts each run.

1. 0:02 Keep credentials out of scripts
2. 1:14 A secret in an uploaded script
3. 2:06 Nightly regression
4. 3:03 One-off scheduled run
5. 3:21 Manage schedules
6. 3:48 Pointer to CI

Manage test secrets and schedules.

When to schedule

• Nightly regressions catch performance drift before standup.
• Hourly probes are small smoke runs that check availability.
• Weekly load reviews are bigger runs you compare with the prior week.

For runs your CI pipeline starts, see Run tests from CI instead.

Create a schedule

1. Open the test and switch to the Schedules tab.

2. Click New schedule.

3. Enter a cron expression. Maxoperf accepts standard 5-field cron syntax. Check the next few fire times in the preview.

4. Pick a timezone so daylight-saving changes do not move your nightly run.

5. Name the schedule if you want, for example nightly-baseline or hourly-smoke.

6. Save. The schedule starts on the next matching time.

   

   Test detail Schedules tab. Each row shows the cron expression, timezone and next fire time. Pause or delete a schedule here.

Cron quick reference

Pattern	Meaning
*/15 * * * *	Every 15 minutes
0 * * * *	Every hour, on the hour
0 2 * * *	Every day at 02:00
0 6 * * 1-5	Weekdays at 06:00
0 0 1 * *	First day of every month at midnight

Pick a quiet time

Run heavy regression tests outside business hours. Then they do not collide with development work or peak production traffic.

Pause or delete a schedule

From the Schedules tab you can pause a schedule or delete it. A paused schedule stops firing and keeps its definition. Runs already in progress when you pause finish normally.

Where to go next

• Run tests from CI: start runs from your build pipeline.
• Build reporting dashboards: track recurring-run results over time.
• Read run results and logs: read each scheduled run.