Record

How to record

1. 1Open the site in Chrome. Recording cannot attach to chrome:// pages or the Chrome Web Store.
2. 2Open QA Studio Pro and press Record.
3. 3Do the journey: click, type, navigate, upload, drag, dismiss a dialog — whatever the flow actually is.
4. 4Press Stop. That session is now a flow you can edit, replay, or export.

What gets captured

• Clicks — left, double, right, middle, with optional offsets
• Typing, including contenteditable
• File uploads
• Drag and drop
• Hovers and keypresses
• Dialogs
• Scroll
• Navigations, including SPA soft navigations

Recording scope

Recording is limited to the tab where you start and to tabs in that tab's opener lineage. The extension does not record unrelated tabs or browse your history outside that scope.

Sensitive fields

Sensitive field masking is on by default. Values typed into fields identified as sensitive (passwords, cards, OTPs) are stored as {VAR} placeholders rather than raw text. Fill the real values as variables before you replay.

After you stop

Edit any step. Add waits, asserts, and variables. Optional advanced steps you can insert: extract, condition, loop, API call, script, network mock, prompt/OTP. Keep the recording to one journey. A smaller flow is easier to replay and cheaper to fix.

The debugger banner

Chrome shows a debugger banner while the extension attaches the debugger API. That API is how record and replay fire real input events. The banner is expected — not a malware warning. See permissions if you want the longer version.

Honest limits

• Debugger cannot attach to chrome:// or the Chrome Web Store.
• Closed shadow DOM is session-scoped and can still fail on some hosts.
• Virtualized lists need a recorded scroll.
• File-upload replay needs an absolute path set after you record.
• Complex rich-text editors may need a script step.