Replay
Autonomous app testing
Start new thread

Replay QA - Replay QA tells you what is broken before your users do

by
•
Add your GitHub repo for continuous testing, or drop in a URL for a one-time check. Replay QA explores your app, records every session, finds real bugs, and gives your coding agent the root cause and fix. Try for free: qa.replay.io

Add a comment

Replies

Best

the part that stands out is handing the root cause and fix straight to your coding agent. most QA tools stop at "here's a bug" and leave you to reproduce and diagnose it, which is honestly 80% of the actual work. closing that loop into the agent that can already fix it is the right instinct, the bug report was never the valuable part.

Hunter

frame this, ?makers!

Maker

 couldn’t have said it better ourselves!

Root-cause handoff to coding agents feels genuinely useful. How do you decide which flows Replay QA explores first?

Maker

 this is handled by our custom-built QA harness. Our QA agent starts by acting as naive as possible, starting with the root page, and analyzing it for what's actually there. With each successive analysis pass, our agent "learns" more and more about what your app is, what it's intended purpose it, and what end-to-end user journeys exists. It then catalogues each user journey, writes Playwright tests against them and executs them by puppeting the app in the browser—all while capturing deterministic runtime recordings (Replay Recordings) that are then analyzed by our agents to identify issues. We have a baked-in triage system that does what human teams do... prioritize what to do first for maximum impact.

Hunter

   for full disclosure, we could add that might not replace every kind of testing, but it will catch the obvious broken flows before your users, clients, or visitors do ✌️

The "give your coding agent the root cause and fix" handoff is the part I'm most curious about — I run multiple coding agents on a monorepo and the painful step is always getting the bug reproduced inside the agent's context. Is the handoff a replayable trace the agent can actually step through, or a text summary of the root cause? Congrats on the launch — the drop-a-URL one-time check is a smart low-friction entry point.

Maker

 Exactly the right question. The useful handoff is a replayable trace the agent can step through, with the relevant context and state, not a glorified text summary. The goal is to remove the “can you reproduce this?” tax before the agent starts working.

Congratulations on the launch!

Hunter

thank your for the support! what site would you test first? start here:

Super cool! Just signed up, put in Git.Law, and it worked out of the box.

I've been looking for something like this.. surprisingly.. not found anything so simple and easy to use. Congrats on your launch.

Maker

 let us know how the results are for (awesome service btw!!!) ... hopefully it found something you weren't even aware of! Feedback is always welcome.

Hunter

I've been looking for something like this.. surprisingly.. not found anything so simple and easy to use.

 exactly. definitely is an opinionated piece of software, thoughtfully crafted. S/O to ?makers for their great work.

put it simply in today's newsletter: "Recording over screenshots is the right foundation, and no other AI QA tool has it." Source:

Is there a way to give it a test email to enter a logged-in area of our browser-based software? Without giving Github access, just to act as if it's a real user setting up an account.

Maker

 Username and password auth or magic links are the easiest way to get the AI to login. Just tell the chat "login with this username and password".

If you only have social logins like login with google then we would likely require a staging environment to test against since login with google is built from the ground up to stop bots.

We are working on workaround where we just pull up the browser ask you to login and then the AI picks up from there. Driving an E2E test through a 3rd party production login is an age old E2E testing problem.

Congrats on the launch folks! Can’t wait to take it for a spin

Maker

 thx!! Would love to hear about your experience when you do.

Hunter

 lfg! thanks for your support, get started here: - enjoy!

This is awesome! I'm looking forward to digging into this. Might write a forum when I do. Congrats on the launch. Nice to see in the mix. 🤩

Maker

   yeah, we're pretty stoked we found him! Don't hesitate to reach out if you have any questions or have any feedback. We've got a bad case of beginner's mind over here (in the best way possible 😃).

Hunter

 thank you for your continuous support, Tessa! appreciate you. feel free to add your review here:

Hunter

 also looking forward to what's next at 👀

the root cause handoff to a coding agent is the part that stands out to me, most bug tools stop at 'here is a recording' and leave you to figure out the actual cause yourself. when it explores the app on its own rather than following a fixed test script, how do you keep it from wasting time down paths a real user would never take?

Maker

 what you're asking hits on exactly what we do that sets us apart from anyone else out there. Our initial product captured deterministic runtime recordings, and then gave you the DevTool interface to time-travel the recording to find root cause yourself. We've now given agents the skills and the harness to do the time-traveling for you. Built upon our years of experience building debugging tools, here at Replay, and the 10yrs Brian Hackett (CEO) spent at Mozilla working on their devTools, we learned what agents need to keep them from going down rabbit holes and wasting time. Check out this Timetravelogue deep-dive by Mark Erikson to get a sense of our approach. (Keep in mind, this is Mark using Replay MCP which is now one of the enabling layers of Replay QA)

Post 1: How Replay MCP Helped Find a React Bug Faster than Dan Abramov Did


Post 2: Improving Nadia’s “Debugging with AI” Results Using Replay MCP

Hunter
Maker

 hey I work on the replay team specializing in exactly this let me know if you'd like to setup a call to discuss how to make the most use of replay in a typical Builder/Critic feedback loop.

Congratulations. And happy product launch.

Hunter

thanks for the support! what site would you test first? start here:

First
Previous
123
Next