TestRouter

In progress: TestRouter is currently under active development.

Coding agents are making it easier to create software quickly. The bottleneck is shifting from writing code to knowing whether the product still works after each change. TestRouter gives teams one reliable place to ask:

Is this change safe to ship?

TestRouter is a visual QA verification layer for modern software teams.

Instead of treating testing as scattered scripts and CI jobs, TestRouter gives teams a dashboard for defining, managing, and running the real user journeys and app areas they want checked. On pull requests, TestRouter runs those journeys in a browser the way a QA tester would: visiting pages, clicking through flows, checking visible states, and capturing evidence when something breaks.

Example checks include:

• a visitor signs up from the pricing page
• a user signs in and reaches the dashboard
• an admin invites a teammate
• a customer updates billing details
• a user uploads or downloads a file
• a key page still renders correctly after a UI change
• an important form can be completed end to end

The goal is not to replace every existing test framework. The goal is to make product-level, visual QA checks easier to define, run, and trust.

Why It Matters

AI can help teams generate code faster, but generated code still needs evidence before it ships.

Real QA-style testing is difficult because it often depends on:

• authentication
• test users
• safe staging data
• preview environments
• flaky browser behavior
• external services such as email, billing, and webhooks
• clear failure reports that humans can act on

TestRouter is focused on those practical bottlenecks.

How It Works

At a high level, TestRouter:

1. connects to a codebase and preview environment
2. discovers or defines important user journeys
3. runs those journeys as browser-based visual QA checks
4. manages test auth and state safely
5. returns clear evidence in the dashboard and on pull requests

Teams can also define, manage, and run flows directly from the TestRouter dashboard. When a pull request opens, TestRouter can run the relevant checks against the preview environment and report back with a pass/fail signal, screenshots, traces, logs, and likely cause when something breaks.