Separate e2e test repos hide breakage; Testward surfaces failures at review

Separate e2e test repos hide breakage until after code merges, but Testward surfaces failures during PR review. [DevTo]

── What shipped ──

QA automation engineer Gabriel Holmes released Testward, a GitHub App that runs on every pull request in the application repository. A one‑line .testward.yml file lists the automation repo(s). For each PR, Testward extracts every changed textual anchor—data-testid, aria-label, route strings, visible copy—and greps the linked spec files for matches. When a match is found, the App runs a lightweight LLM filter to discard false positives and posts a comment on the PR with the spec path, the changed selector, and the expected behavior. The developer can address the issue before merging. [DevTo]

── Why it matters ──

Testward shrinks feedback loops dramatically: in the split‑repo model a PR passes CI, merges cleanly, and only hours later a scheduled run in the automation repo fails, forcing a back‑and‑forth that can consume an afternoon. By surfacing the same information at review time, the incident becomes an instant comment. It also keeps cost with the code author; the developer who introduced the change must fix the breakage, rather than the QA team bearing the triage burden. Finally, the dependency is purely textual—selectors, role queries, and route strings exist independent of repository boundaries—so a static scan can detect breakage without executing the test suite, something in‑repo tools cannot do when tests live elsewhere.

── Editor's take ──

The real win is not the novelty of a GitHub App but the reminder that test ownership should be visible at review time. Companies that silo e2e suites are outsourcing their own quality gate. A cheap static‑anchor check like Testward forces the dependency into the PR, making the cost of breaking a test immediate and personal.

Reader poll

Which strategy do you use for end‑to‑end testing?

• All tests live in the same repo as the app
• Tests live in a separate automation repo
• Separate repo plus static anchor checks (e.g., Testward)
• Custom CI tooling that links repos