Test plans and schedules
Group test cases into named plans, run them together, and run a plan every night.
A test plan is a named selection of test cases in one project, such as "Smoke" or "Release readiness". Test cases stay independent: the same test case can be in several plans, and fixing it once fixes it in all of them. A test case doesn't need a plan.
Open a project and click Test plans.
Create a plan
A plan is created by naming it. Open a test case and type a name in its Test plan field: if no plan has that name yet, it's created, and the test case joins it. Do the same on each test case you want in the plan.
Run a plan
Click Run plan on the plan, or open New run and choose the plan under Or a test plan. Pick the environment and click Start run.
Running a plan starts one run per test case, in the plan's order, all in the same environment. Each run is a normal run with its own page, steps and result, as if you had run it alone. If there isn't room to start all of them, none start.
Each test case must set up its own journey. Don't rely on an earlier test case in the plan having signed up an account or created data: a single failure would then break everything after it.
Schedule a plan
Open a plan, go to Triggers, and turn on Schedule: the plan runs every night at 02:00 on the environment you pick, in the time zone of the browser you saved it from. Click Save triggers.
- If the project has no environment yet, add one first.
- If there isn't room to run the plan one night, or the plan is empty, that night is skipped and the next one is booked.
- On the night clocks change, a skipped time runs at the next minute that exists, and a repeated time runs once.
Scheduled runs show "Schedule: <plan>" as their trigger.
Run a plan on pull requests
A project can run one plan on every pull request, against the PR's preview deployment, with the results as a GitHub check. Choose the plan in Settings → Integrations → Pull requests. See Pull request testing.
Choosing what to group
Keep plans small and named after a decision someone makes:
- Smoke: the few journeys that must work before anything else is worth checking.
- Release readiness: what you check before shipping.
- One area: checkout, onboarding or billing.
Avoid an "everything" plan. A plan that always has one unrelated failure teaches reviewers to ignore it.
Didn’t find it?