Scheduled runs
Run a suite every day, every weekday, every week or every few hours, and get an alert when a scheduled run fails.
A schedule runs a suite by itself at the times you choose, such as Parcel's release suite every weekday at 09:00, so a problem that slipped in overnight is waiting for you in the morning. It tests the addresses you pick, and when a scheduled run fails, the schedule's owner gets an alert.
A schedule always belongs to a suite, so make the suite first, as Suites shows. Adding or changing a schedule needs the Manage projects permission.
Add a schedule Link to Add a schedule
Step 1: Open the suite
Open Tests, pick
releaseunder Suites in the sidebar, and find Schedule under the suite's recent runs. Press Add schedule. The button appears once the suite holds at least one test.Step 2: Choose how often
How often offers Every day, Every weekday, Every week and Every few hours. The first three take a Time, and Every week also takes a Day. Every few hours takes an Interval of 1, 2, 3, 4, 6, 8 or 12 hours, counted on the hour from midnight, so every 6 hours runs at 00:00, 06:00, 12:00 and 18:00.
Step 3: Choose the time zone
Time zone starts with your browser's own. To use another, type its name, such as
Europe/LondonorAmerica/New_York. The times you chose follow that zone's clock, including its changes for daylight saving.Step 4: Choose the addresses
Pick an address under Address for each app in the suite. An app with one address has it picked already.
An address on your computer works only while your computer is connected at the scheduled time, so a deployed address is usually the better choice. When your computer is not connected at that time, no run starts and the schedule says "The scheduled address is offline."
Step 5: Save it
Press Save schedule. The schedule appears as one sentence that names its time zone by its place, and under it Next run with the date and time in your own time zone:
Output Every weekday at 09:00, London
A suite can have more than one schedule, such as one in the morning and one in the evening, and each has its own row.
What a scheduled run checks Link to What a scheduled run checks
Each scheduled run is an ordinary run of the suite as it stands at that moment, at the addresses the schedule names. It appears in Runs with Scheduled as how it started and in the suite's Recent runs, and you read it as Read a run shows. Scheduled runs count towards your plan in the same way as the runs you start yourself, as Plans and runs explains.
If Rehearsal could not start a scheduled run on time, for example during an outage on our side, the schedule runs once as soon as it can, however many times it missed, then goes back to its usual times.
When its latest scheduled run did not pass, the schedule says so in red under its sentence, such as "The tests failed.", and when no run could start it says why, such as "Your workspace has used its included runs." The line goes while the next scheduled run is under way, and stays gone if that run passes. A run someone stopped leaves no line.
Alerts when a scheduled run fails Link to Alerts when a scheduled run fails
When a scheduled run fails, is blocked or cannot start, the schedule's owner gets an alert on the bell headed release needs a look. More failures in a row update that same alert with a count, such as "3 scheduled attempts failed.", rather than adding new ones. Once a scheduled run passes on every screen, the alert closes and a second one says release recovered.
A run we could not finish and a run someone stopped are not failures, so they raise no alert and leave an alert that is already open as it is. The schedule still shows a run we could not finish in red under its sentence, as "Rehearsal could not finish the run.", although it counts as no failure, and Runs we could not finish explains what happened to it.
Email reaches you less often than the bell. Rehearsal emails the owner about the first failure, the first time a run could not start and the recovery, not about every attempt in between. You choose them in Settings, then Notifications, then Email. Email chat and schedule alerts turns them all off, and the page's Scheduled runs card has two switches, A scheduled run fails and A scheduled run recovers. The Browser page has the same two switches for notifications in your browser. The alert on the bell arrives whatever these switches say.
Pause, change or remove a schedule Link to Pause, change or remove a schedule
- Pause. Turn off the switch beside the schedule, and it says Paused. Turning it on again starts from the next scheduled time, with nothing to catch up.
- Change. The pencil opens the schedule with what it holds, and saving it moves the next run to the new times.
- Remove. The bin removes the schedule after you confirm. The runs it already made stay in Runs.
The owner is the person who created the schedule, or who last edited or resumed it, so editing or resuming one makes you its owner. Scheduled runs then start as you, and the alerts come to you.
Good to know
A schedule runs with its owner's permission. If the owner leaves the workspace or loses Manage projects, the schedule pauses and says "The schedule owner lost access. Resume it to become its owner." Anyone with Manage projects can turn it back on and become the owner. Removing the suite or its project pauses the schedule too, without an alert.