In mabl, you can set up scheduled plan runs to get consistent feedback on ongoing development work. Scheduled runs are also helpful for optimizing resource utilization because you can run tests during off-peak hours.
This article explains how to run mabl tests on a schedule
How to set up a schedule
When you create or edit a mabl plan, you can add a schedule in the Triggers section. Add the Timer or Schedule depending on how often and when you want the plan to run:
- Timer: Set the plan to run in intervals, starting from the time you save the plan. The minimum is five minutes and the maximum is 168 hours (seven days).
- Schedule: Set the plan to run at a specific time on specific days. A plan can accept multiple triggers by schedule.
The Triggers section also includes the Deployment trigger, which is turned on by default. This trigger is used for mabl deployment events and is necessary if you wish to integrate this plan with your CI/CD tool.
Scheduled runs is only supported for plans that execute in the cloud. If you want to schedule local or CI runs, you'll need to configure that manually with your own scripts.
The Timer and Schedule triggers are not supported for branched plan runs. If you want to set up a recurring trigger for a branched version of your plan, use deployment events and check out the scheduling capabilities for your team’s CI/CD tool.