Regression Testing

Regression testing runs one or more predefined test groups against every PR preview deployment and posts the results to the PR. Reviewers see pass/fail results directly in GitHub without leaving the review, and broken changes get caught before merge.

Use this when you already know the flows that matter and want them verified the same way on every PR. To also catch issues nobody wrote a test for, pair it with the Exploration agent.

See Pull Request Testing for prerequisites, supported providers, and troubleshooting.

Setup

1. Open your project and go to the PR Testing tab.
2. Enable Test groups for PR runs and select one or more test groups to run on pull requests. Enabled tests in the selected groups will execute against every new deployment preview.
3. In Integrations → Vercel, connect Vercel and choose the matching Vercel project.
4. If Vercel deployment protection is enabled, add a bypass token.

Optional: in Integrations → GitHub, choose a target branch if you only want PRs aimed at one base branch, such as main, to trigger automatic runs.

Every new preview deployment now triggers the selected test groups automatically. Each group runs as its own batch with its own GitHub check and PR comment.

Disabled tests are skipped in PR runs but remain available for manual runs.

If a selected group uses a Preparation Test, PR runs honor it too: the prep test runs first, web consumers reuse the saved session, and non-web consumers stay in that group’s batch without browser-session reuse.