Groups and schedules

Run several tests as one batch, by hand or on a timetable.

Groups

A group is a set of tests that run together as a batch. You choose how the batch runs:

• At once: tests run in parallel, up to your plan’s limit of runs at once.
• One after another: tests run in order, one at a time.

The batch page shows the result of every test and the first failure.

Logging in once

Give a group a preparation test (group page → Login) that signs in. It runs first in every batch; the other tests start already signed in, from the cookies and storage it ended with. If it does not pass, the others are marked blocked, not failed, and do not count toward your quota. Re-running failed tests within a day keeps the same login. For apps that rotate refresh tokens, choose to log in before each test instead.

Schedules

Add a schedule to a group to run it automatically: hourly, daily or weekly, or with a cron expression such as 0 9 * * 1-5 (09:00 on weekdays; at most every 15 minutes). Pick a time zone so “every day at 09:00” means 09:00 where you are; a time skipped by a clock change runs at the next valid time, and a repeated one runs once.

Notifications

Add channels to be told when a batch finishes: email, Slack, or a webhook. Webhook deliveries are signed so you can check they come from us.

Reports and sharing

Download a JUnit XML report for any batch to use in your own tools.

To show a result to someone outside your team, open the run and choose Share: the link shows the steps, the outcome and screenshots for 1, 7 or 30 days, and you can revoke it. Screenshots that may show a typed login or code are left out unless an owner or admin includes them along with the video.

Counting runs

Every test run in a batch counts toward your monthly quota, except runs that fail on our side. Scheduled batches wait behind CI-triggered batches when capacity is tight.