Back to feed
Dev.to
Dev.to
7/3/2026
Your E2E tests live in a separate repo. That's why nobody sees the breakage coming.

Your E2E tests live in a separate repo. That's why nobody sees the breakage coming.

Short summary

E2E tests in separate repos prevent developers from seeing failures caused by their changes because CI tooling can't cross repo boundaries. The author proposes anchor extraction—scanning test repos for selectors and routes touched by PR diffs at review time. They built Testward, a GitHub App automating this cross-repo dependency detection.

  • •Separate test repos hide test failures from developers because CI tooling can't link changes across repo boundaries
  • •Most tests depend on textual anchors (data-testid, routes, aria-labels) that PR diffs can safely extract and match
  • •Testward automates scanning linked repos' specs for broken anchors before merge, surfacing consequences at review time

Generated with AI, which can make mistakes.

#ai-tools
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

How to know which tests a PR will break — before CI runs
Dev.to
A One-Second Static Check for E2E Selector Drift
Dev.to
The hard part of PR testing often comes before the test
Dev.to
The original title is: "The Frontend Testing Problems That Happy-Path E2E Tests Usually Miss"
Dev.to