Works alongside Replay QA
Replay QA vs Playwright
Replay QA is built on Playwright: it writes and runs Playwright tests. The difference is what happens when a test fails because your app is broken.
The short version
- Playwright Test Agents plan, generate and heal tests. Replay QA explores, tests, and diagnoses the app.
- When a failure looks like a real app bug, Playwright’s healer marks the test test.fixme() so it is skipped. Replay QA reports the bug with root cause and a suggested fix.
- Playwright MCP drives a live browser. Replay MCP queries a recorded one. They fit together.
At a glance
| Dimension | Replay QA | Playwright |
|---|---|---|
| What you provide | A URL or a GitHub repo. No setup beyond that. | Install Playwright, a seed test, and init-agents for your agent. |
| Test suite | None needed. Writes and runs its own Playwright tests. | Test files in your repo, generated or hand-written. |
| How bugs are found | Agents explore the app and discover user journeys themselves. | Planner explores the app and writes a test plan. |
| Evidence | Deterministic time-travel recording of every session, plus video and annotated screenshots. | Trace viewer: DOM snapshots, screencast, console, network. |
| Root cause analysis | Agents time-travel through the recording; each report has a confidence score. | Healer repairs test code only. |
| Suggested code fix | Every bug report includes a suggested fix for a coding agent. | Fixes the test; skips it if the app looks broken. |
| Needs real user traffic | No. Tests before you ship. | No. |
| Native mobile | No. Web apps, tested in Chromium. | Mobile browser emulation only. |
| Coding agent access | Replay MCP server, REST API, and PR comments. | Playwright MCP; agents for Claude Code, Codex, VS Code. |
| Pricing | Free (25 credits/mo), Starter $20/mo, Pro $200/mo. | Free and open source (Apache-2.0). |
Based on Playwright’s public site and documentation, last verified October 14, 2026. Products change; check the sources for the latest. playwright.dev/docs/test-agents · github.com/microsoft/playwright/blob/main/packages/playwright/src/agents/playwright-test-healer.agent.md · playwright.dev/docs/trace-viewer · github.com/microsoft/playwright-mcp
Product names are trademarks of their respective owners and are used for identification only.
How they work together
Built on Playwright
Replay QA writes and runs its own Playwright tests, so the framework you already trust is under the hood.
Two MCP servers, opposite directions
Playwright MCP lets an agent drive a live browser. Replay MCP lets an agent pull bug reports and time-travel debug a recorded run. Give your agent both.
Where Replay QA goes further
App bugs get diagnosed, not skipped
Playwright’s healer is designed to get tests passing, and marks a test test.fixme() when it believes the functionality is broken. Replay QA treats that failure as the finding: it time-travels through the recording to root cause and suggests a fix.
Nothing to seed
The Playwright planner needs a seed test to set up the environment. Replay QA starts from a URL or GitHub repo.
A deterministic recording
Playwright traces capture snapshots around each action. Replay QA records every DOM mutation, network call and JS frame, so agents can inspect any moment of the run.
Where Playwright is stronger
Free, open and in your repo
Playwright is Apache-2.0, runs anywhere, and its tests are auditable files you own.
Cross-browser
Playwright runs Chromium, Firefox and WebKit. Replay QA tests in Chromium.
Choose Playwright if
- You want to own and maintain a test suite yourself, at no license cost.
- You need Firefox and WebKit coverage.
Choose Replay QA if
- You want app bugs diagnosed with a suggested fix, not tests skipped.
- You want exploration, testing and analysis running without maintaining a harness.
What you get
Bug reports your coding agent deserves
Each report is prepared with coding agents in mind. A detailed root cause analysis, a suggested fix, a deterministic runtime recording, and all the context needed to do the job.
Video recording
Watch the failure exactly as it happened.
Annotated screenshots
See where on the page things went wrong.
Root cause analysis
With a confidence score, so you know what to fix first.
Suggested fix
Ready for a coding agent to apply.
Frequently asked questions
Related: All comparisons · Replay QA vs QA Wolf · Replay QA vs Meticulous · Replay QA vs BrowserStack
Test your web app today
Paste a URL or connect a GitHub repo. Free includes 25 credits a month, and an average app uses about 20 credits per full QA run.