Mark Erikson on Replay QA: from time-travel debugging to autonomous QA

Replay QA is an autonomous testing product built on Replay’s time-travel browser-recording technology, which was originally designed as an advanced debugger that could replay application sessions, inspect state at any point, and integrate with React and Redux tooling. After limited adoption of its developer-facing debugging interface, Replay exposed recorded execution data through an MCP server, allowing AI agents to investigate bugs using information such as stack frames, variables, component renders, network activity, and Redux dispatches. Replay QA applies this capability to GitHub pull-request workflows by generating and running user journeys for a website, recording those sessions, and identifying potential broken flows, accessibility problems, security issues, rendering slowdowns, and network inefficiencies over time. Mark Erikson described an example in which an agent identified a WebSocket compatibility issue in Replay’s Chrome 108 runtime and prompted the rapid addition of tools for inspecting WebSocket traffic. The company has also expanded its React analysis system so it can instrument minified production bundles from common bundlers without source maps, enabling render and performance analysis across a much larger share of recordings.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.