Which Selenium tests will this PR break?

Locators are the weak point

Selenium suites lean on locators — ids, names, CSS and XPath — usually wrapped in page objects. When a PR renames an id or restructures markup, the locator silently stops matching. The page object goes stale and every test through it fails, often with a generic NoSuchElementException that buries the real cause.

What Testward does

• Reads each PR diff and extracts the anchors it touches — ids, names, CSS classes, route literals, visible text.
• Scans your Selenium tests and page-object files (same repo or a linked repo) for ones referencing those anchors.
• Confirms with an LLM pass and names the page objects and tests likely to break.
• Posts a single sticky PR comment with the affected files and reasons.

Cross-repo and Page Object Model aware

Selenium suites are usually in their own repo. Link it once:

# .testward.yml
automation_repos:
  - your-org/selenium-suite

Because Testward scans page-object files, it flags the page object holding a stale locator and the tests that route through it. Cross-repo setup →

Make locators durable

The long-term fix is stable, intentional hooks. See selectors that don't break.