Preparation Test
A Preparation Test lets one test in a group log in (or perform any setup), save the resulting browser session, and have every other test in the same group reuse that session. This avoids re-running login steps in dozens of dependent tests and keeps your suite fast.
How it works
- Pick one test in a group and mark it as the Preparation Test.
- Whenever the group is run (manually via Run all, on a schedule, or via webhook), the prep test runs first.
- After the prep test completes successfully, its final browser session is written to a one-shot Kernel profile that's scoped to that single batch.
- Web tests later in the same batch open their browser with that profile attached read-only, so they start already logged in.
- Non-web tests still stay in the same prep-first batch ordering, but they do not load the saved browser session.
- Once every test in the batch finishes, the profile is deleted automatically.
Each batch gets its own isolated session, so:
- The prep test always starts from a clean slate — no state leaks in from a previous run.
- Two batches can run in parallel without colliding on the same session.
- Nothing is left behind to grow over time.
If the prep test fails, the dependent tests in that batch are cancelled and the profile is still cleaned up.