# Choose the tests that cover your change

Use the behavior changed by a pull request to choose browser tests. Zerocheck runs the tests you select; it does not infer coverage from the code diff.

Use the behavior changed by a pull request to choose browser tests. Zerocheck runs the tests you select; it does not infer coverage from the code diff.

## Who it is for

- Role: Pull-request author or reviewer
- Company: Teams with a growing browser suite
- Trigger: A change affects several user journeys

## Why this is underserved

- A file diff alone does not capture every affected user outcome.
- A fast subset is useful only when the selection is appropriate.
- New behavior needs a new expectation, even if existing tests pass.

## The workflow

Before: The author changes an account-settings form and assumes the existing smoke suite covers it.

After: The reviewer identifies the changed outcome, runs the related saved tests and adds a new test when the checklist misses it.

## How Zerocheck handles it

1. Write down the user-visible behavior affected by the change.
2. Choose existing tests from the web app, or select YAML paths in the CLI.
3. Draft an additional test when the expected outcome is new.
4. Run the broader regression suite according to the team’s release policy.

## Good fit when

- A web app and a repeatable user flow
- A test environment, test accounts and an explicit expected outcome

## Frequently asked questions

### Does Zerocheck select tests from Git diffs?

No. Selection is manual in the web app or by file path in the CLI.

### Can it create tests from a requirement?

Describe the user flow and expected outcome, or paste checklist items. Zerocheck drafts and runs browser steps for that input.

---
Canonical: https://tryzerocheck.com/use-cases/change-aware-testing/
Updated: 2026-09-14