Link your automation repo

When your E2E/automation suite lives in a separate repo from your app, point Testward at it. Then every app PR is checked against your automation, and Testward flags the specs that will break.

1. Install Testward on both repos

Install (or "Configure") the GitHub App on both your app repo and your automation repo — or just install it org-wide. Testward needs read access to the automation repo to scan its specs.

2. Add .testward.yml to your app repo

In the root of the app repo, add a file named .testward.yml listing the automation repos to check:

# .testward.yml  (in your app repo root)
automation_repos:
  - your-org/web-e2e
  - your-org/mobile-automation

That's the whole config. Inline form works too: automation_repos: [your-org/web-e2e].

3. Open a PR

On the next PR in your app repo, Testward extracts the selectors, routes, and endpoints your change touches — data-testid, element ids, getByTestId/getByRole args, URL paths — and scans the linked automation repos for specs that reference them. It then names exactly what breaks:

🚨 Automation this PR may break:
- your-org/web-e2e → tests/login.spec.ts — clicks [data-testid=login-btn]
  (renamed to signin-btn) and asserts the /dashboard redirect that changed to /home

What it looks for

• Test ids: data-testid/data-test/data-cy/data-qa/data-automation-id, React Native testID, Android resource-id
• Accessibility: aria-label, accessibilityLabel (RN/iOS), content-desc (Android)
• Element attributes: name, placeholder, alt, title, element ids
• Visible text: button/link/label text that locators like getByText/getByRole({name}) depend on
• Routes & endpoints: URL paths like /checkout

It matches the actual selector/route/label values — not framework syntax — so it's framework-agnostic. Renamed or removed anchors are the breaking ones; an LLM pass then filters anything that doesn't actually break, so you get signal, not noise.

Works with your framework

Because it matches the underlying selectors, routes, and text rather than a specific tool's API, it works across:

JS/TS, Python, Ruby, Java, C#, Kotlin, Swift, Go, PHP, and .feature/.robot specs are recognized.

← Back to Testward · Test history setup