Which Playwright specs will this PR break?

The Playwright maintenance problem

Playwright tests are coupled to the app through selectors, routes and visible text. That coupling is the whole point — but it means the suite breaks whenever the app changes in a way the tests didn't expect. The breakage is invisible until CI runs, and by then the dev has context-switched away.

The usual signals don't help: the PR diff is in src/, the failing test is in tests/, and nothing in code review connects the two. On teams where the Playwright suite lives in its own repo, there's no connection at all.

What Testward does

On every pull request, Testward:

• Reads the diff and extracts the anchors a change touches — data-testid, getByRole/getByText targets, route literals, aria-labels, ids, placeholder and visible text.
• Scans your Playwright specs (same repo or a linked repo) for specs that reference those anchors.
• Runs an LLM confirmation pass that names the specific specs likely to break and explains why.
• Posts one sticky comment on the PR: "🚨 Automation this PR may break" with the file paths and reasons.

It works across repositories

Most Playwright-heavy teams keep E2E in a dedicated repo. Add a one-line config to the app repo:

# .testward.yml
automation_repos:
  - your-org/e2e-playwright

Now a frontend PR in the app repo flags the Playwright specs it will break in the E2E repo — the connection no other review tool draws. See the cross-repo setup →

Selectors that survive refactors

The best fix for a brittle suite is stable hooks. Testward recognizes the data-testid / getByTestId pattern and flags when a PR renames one a spec depends on. If you want to harden your suite first, our guide on choosing selectors that don't break walks through it.