Replay QA overview

Replay QA is an autonomous QA service for web apps. Give it a running application and it explores the product like a user, turns important flows into reusable journeys, tests those journeys in Replay Browser, and reports bugs with the evidence needed to reproduce and fix them.

You do not need an existing test suite or a list of reproduction steps. Replay QA can start from an application URL and guidance about what the product should do.

Launch Replay QA

How Replay QA works

1. Explore the app. An AI agent drives the application in a real browser to discover its screens, actions, and important workflows.
2. Create journeys. Replay QA saves meaningful flows—such as signing up, searching, or checking out—as journeys that can be tested again.
3. Run the journeys. Test runs exercise those journeys in Replay Browser and capture a deterministic runtime recording of what happened.
4. Investigate findings. When a run uncovers a problem, Replay QA uses the recording to trace the symptom back to its root cause.
5. Report actionable bugs. Each confirmed bug includes the observed behavior, evidence, root cause analysis, and a suggested fix.

The project remains useful after its first pass. Start another exploration to expand coverage, rerun journeys after a change, or connect GitHub to test new deployments continuously.

Connect the application

Replay QA needs a running version of the application that its test browser can reach.

Public URL

For a deployed app or preview with a public URL, create a project and enter that URL. Replay QA can begin exploring without a tunnel or CI configuration.

Localhost or a private network

For an app that only runs on your computer, use the managed reverse proxy. The outbound tunnel lets Replay QA reach the local app without deploying it or publishing it directly to the internet.

Test an app running on localhost →

The same setup can reach internal hostnames and services available through your computer's VPN or private DNS.

A build inside CI

If the application only exists inside a GitHub Actions runner, keep the app and tunnel alive for the complete test run with the FRPC CI integration.

Run Replay QA against a private CI build →

Build useful coverage

You can shape what Replay QA tests without writing browser automation.

• Instructions focus exploration on the workflows, roles, and outcomes that matter most.
• A design document gives QA a source of truth for intended behavior.
• Test logins and variables let journeys cover authenticated areas without putting credentials into test steps or bug reports.
• Additional explorations discover new journeys as the product grows.
• Polish passes check journeys for focused classes of issues, including user experience, accessibility, visual behavior, layout stability, and network performance.

Review test results

A Replay QA project organizes its output around the work it performed:

• Overview summarizes current QA activity, open bugs, recent test runs, and explored journeys.
• Bugs collects confirmed findings and their severity, evidence, root cause analysis, and suggested fix.
• Test Runs shows each round of journey execution and the result of every journey it exercised.
• User Sessions captures submitted sessions when a project is configured to accept them.

Bug reports can be copied or downloaded as Markdown for a coding agent. After applying a fix, rerun the affected journey to verify the behavior against the same flow.

Test changes from GitHub

Connect a repository with the Replay QA GitHub App to run QA when new application builds become available.

• Main branch: test a known deployment URL when a new main-branch deployment goes live.
• Pull requests: test preview deployments reported by GitHub and post the result back to the pull request.

GitHub is optional. A project can test a public URL or a reverse-proxied local app without connecting a repository.

Get better root cause analysis

Replay QA works with any browser-based web app, with especially deep runtime analysis for React applications. Publish production source maps so reports can map compiled code back to the original source files and line numbers.

Publish your app with source maps →

FAQ