Guide

    Create a schedule

    Run a test on its own, on an interval or at a time you choose

    Steps

    1. Open Schedules under Data Management

      The page splits in two: defaults that are always there, and custom schedules belonging to your workspace. Both show up wherever a schedule can be chosen.

    2. Check the defaults first

      If one of these fits, use it. A default costs nothing to maintain and is already available in every picker, so there is no reason to make a custom schedule that duplicates one.

    3. Name a custom schedule

    4. Recurring Interval reaches further than the defaults

    5. Switch to Cron for anything calendar-shaped

      Minute, hour, day-of-month, month, day-of-week. Because the expression is already a working weekday-9am example, the quickest way to your own is usually to edit it rather than start from scratch.

    6. Set the timezone deliberately

      Pick the zone your business runs in rather than UTC if the time is meant to track local working hours. A 9am UTC job drifts to 10am London through British Summer Time; the same expression set to Europe/London stays at 9am all year.

    7. Read the row you get back

      Pause is the safe way to stop automated runs while you investigate something. Deleting the schedule instead would strip it from every test using it.

    8. Open the test you want to automate

      The same control appears in the create wizard's Automation step, and on a batch, where it runs every test in the batch in parallel each time it fires. Mission tests have no schedule control at the moment.

    9. Pick from the same two groups

    10. Notice the second alert toggle

      Worth switching the schedule alert on. An automated test that quietly starts failing at 9am every day is exactly the thing nobody notices until someone goes looking.

    11. Save, and check the Schedule column