Chrome extension
Features
Local-first record and replay for people who want a real-site flow without writing a test harness first. Manifest V3. This browser. No account.
Journeys
A journey is one user path, recorded as one flow. Login, payment, a config change — each is its own recording. You compose them later. You do not capture “the whole app” as a single tape.
Small flows are the product idea. They replay more reliably, they swap when staging and prod differ, and when one step breaks you edit that journey instead of throwing away an 80-step script.
After capture you can edit steps, add waits and asserts, and insert optional advanced steps (extract, condition, loop, API call, script, network mock, prompt/OTP) when the UI needs them.
Folders
A folder is a feature suite. Group the journeys that belong together — login, then add to cart, then pay — and run a selected set in order.
Runs are fail-fast. If login fails, payment does not start. You debug the first break instead of watching later flows fail because the session never existed.
Folders are local, like everything else. They are not shared projects, not a test-management workspace, and not a cloud run history.
Environments
Keep the flow. Change the data. An environment is a named set of variable values you pick at play time — variables such as {BASE_URL}, {USERNAME}, {PASSWORD}.
Use that for staging vs prod, two test users, or a config matrix (payment × currency, locale, flag). Do not duplicate the whole recording just to change a host name.
Sensitive fields are masked at capture by default. You fill values in the extension; they stay in this browser.
Record & replay
Press Record and use the page. Clicks (left, double, right, middle), typing (including contenteditable), file uploads, drag-and-drop, hovers, keypresses, dialogs, scroll, and navigations — including SPA soft navigations — become structured steps. No selectors to write.
Play uses the Chrome DevTools Protocol to fire real input events. It retries flaky selector resolution and waits for the page to settle. It follows tabs the flow opens, iframes, and open shadow DOM.
Debug in the extension: step status, failure screenshots, run history (newest 50). Then export JSON, YAML, or Playwright TypeScript if you want a file — that handoff is explicit. Replay & debug.
Privacy / local-only
No account. No server. No telemetry. No AI in v1. Flows, variables, run results, and failure screenshots stay in IndexedDB in this browser.
Nothing is transmitted to us. There is no backend for QA Studio Pro and no analytics or crash reporting that phones home. Data leaves the browser when you export a file, or when a step you configure makes an HTTP request to a destination you choose.
Chrome will still ask for permissions that make record/replay possible, and it will show a debugger banner while the debugger API is attached. That is expected. FAQ: local-only · permissions.
What v1 is not
Not a test-management SaaS. Not open-source Playwright reporting. Not AI-powered healing. Not a paid cloud with seats and projects. Those are different products. QA Studio Pro v1 is the Chrome extension: record, replay, organize, export — on your machine.
Honest limits still apply: closed shadow DOM can fail on some hosts, virtualized lists need a recorded scroll, file-upload replay needs an absolute path, and the debugger cannot attach to chrome:// or the Chrome Web Store. FAQ.
QA Studio Pro is free on the Chrome Web Store. No account, no server, no AI in v1.