Skip to main content

Scheduling JobsDirect link to Scheduling Jobs

Beyond running a test session manually or you can trigger it on a recurring schedule and have results delivered to where your team already works.

Scheduling recurring runsDirect link to Scheduling recurring runs

  1. From a test case, folder, or saved test plan, open Schedule.
  2. Set a recurrence (for example, daily at a fixed time — scheduled sessions appear in Test sessions attributed to the scheduler rather than a user, shown with a calendar icon under Started by).
  3. Choose the environment and save.

Scheduled sessions run the same way as manual ones — provisioned on the next available Cloud Agent — and show up in your normal session history (for example, recurring Job: Daily Tests runs).

NotificationsDirect link to Notifications

Once a session completes, results can be delivered automatically to:

  • Email — a summary sent to configured recipients.
  • Slack (available soon) — a message to a configured channel, for every run or just failures.

Configure delivery channels under Settings → Notifications. You can scope notifications per environment or per test plan if you only want, for example, production failures to page a channel.

  • Test Sessions — where results land regardless of how the run was triggered.
  • Agents — how parallel CI-triggered runs are allocated across your fleet.