QA Recorder: record, inspect, replay, test
1. Make a recording code. On the QA Recorder page press "Make recording code". It is valid for 12 hours; "Stop all codes" ends them early.
2a. Record on the original site with the browser extension:
- Download the recorder, unzip it, open chrome://extensions, turn on Developer mode, press "Load unpacked" and choose the folder (Chrome, Edge, Brave, Arc).
- Open the site, click the recorder icon, paste the code, name the session and press Start.
- Let the experienced user work normally. Press Stop at the end.
2b. Record on the exported site: open it with the QA link shown on the page (address + ?wd-record=CODE). A red "QA recording" badge shows. Open any page with ?wd-record=off to stop.
What is recorded: every web call (method, address, status, time, headers, request and reply content up to 256 KB), every click, typed value and page change.
What is never recorded: passwords, hidden fields, card numbers, tokens, cookies, sign-in headers and any field or setting whose name looks secret. These are blanked in the browser before sending and blanked again by our server.
3. Inspect: pick a session, filter by address, status or text, click a call to see headers and bodies. Compare two sessions (e.g. original vs new site) — differences are highlighted.
4. Replay: give the new site's address and press Replay. Each own-site request is repeated from our server and judged on status, reply structure and speed (more than 3× slower and over 1.5 s counts as slow). Requests that change data are skipped unless "Allow writes" is on — only use that on a test copy. Outside servers are never replayed.
5. Playwright test: "Download Playwright test" gives a .spec.ts file that repeats the clicks and typing and checks every recorded request still happens. Hidden values are read from QA_SECRET_1, QA_SECRET_2… environment variables.
npm i -D @playwright/test && npx playwright install chromium QA_SECRET_1=… npx playwright test my-session.spec.ts
Recorder update. Download and reload version 1.0.2 before recording. The extension now captures real clicks, inputs and page changes in isolation, plus browser-observed request method, address, status and time. It no longer collects request/reply headers or bodies; those fields are unavailable for new extension sessions. Exported-site recording still collects redacted call details but is page-based, not a certified activity log.