Guide

    Create a batch

    Group tests that should pass together, and run them in one go

    Steps

    1. Start on Test Batches

      Batches hold standard and parameterised test configs — the ones on Test Config. Mission tests are not offered here.

    2. Name the batch for the moment it runs

      Tags work the same as everywhere else: lowercase, up to ten, used to filter and group the list once you have more batches than fit on a screen.

    3. Optionally put it on a schedule

      In parallel, not one after another — a batch of six on an hourly schedule is six calls an hour, not six spread across it. Worth a thought before pointing a large batch at a short interval. Building a schedule is its own guide.

    4. Pick the tests

    5. Narrow by tag or search

      This is the payoff for tagging test configs consistently. A batch that is "everything tagged acme" takes seconds to assemble and is easy to keep honest later.

    6. Click tests to move them across

    7. Create it

      The alerts toggle on the form is disabled until this point for the same reason a test's is: there is nothing to attach an alert rule to until the batch exists. Reopen it in Edit to switch alerts on.

    8. Know what the row actions do

      Treat play with the same care as on a single test, multiplied by the number of tests attached. Duplicate is the safe way to try a variation of a batch you rely on.

    9. Read the result once it has run

      The counts are the quickest triage you have. A batch that says Completed with a red middle number ran cleanly and found a genuine failure; a Partial usually means something went wrong with the run itself.