Test Case Scheduling
Robonito allows you to construct automated CRON-style schedules to run test cases unconditionally at specific times. This is ideal for continuous validation workflows such as nightly regression pipelines.
Creating a Schedule
Navigate to the Schedules section natively in the left dashboard sidebar and click the New Schedule button.

1. Configure Timeline Properties
The schedule wizard requires absolute definitions for execution timing:

- Schedule Name: Enter a recognizable tracking identifier (e.g., Nightly API V2 Verification).
- Frequency: Define the recurring interval cadence (e.g., Daily, Weekly).
- Timezone: Select the local geographical timezone. The trigger clock is strictly mapped to this boundary.
- Execution Time: Specify the precise 24-hour timestamp at which execution must begin.
- Environment: Select the target compute logic (
LOCALorCLOUD). (Note: Local scheduled execution requires the Robonito host application to remain persistently open on the target machine).
2. Map Test Cases
Configure the execution payload by actively selecting the target test cases:
- Use the search bar to locate specific test flows.
- Select checkboxes to group tests together into the scheduled queue.
- You must select at least one test case to successfully save a schedule.
3. Save
Click Create Schedule. The Robonito orchestration server will natively queue your suite execution.
Managing Active Schedules
All configured schedules are tracked dynamically in the Schedules dashboard.

Schedule Table Overview
| Column | Description |
|---|---|
| Name | The configured schedule identifier. |
| Status | The timeline status (ACTIVE indicates the clock is enabled). |
| Upcoming Run | A computed countdown clock indicating the exact next execution instance. |
| Frequency | The selected recurring cadence. |
| Actions | Open the context menu to Pause, Edit, or Delete the schedule tracking logic. |
When a scheduled countdown triggers, Robonito executes all mapped test cases synchronously and generates a standard execution report aggregating the pass/fail assertions.