2.7 Chrome & Edge Live Recorder Extension

How to record user interactions on live web applications and sync directly to CertiQA test suites.

Recording What You’d Otherwise Have to Describe

Describing a multi-step flow precisely enough for someone else – or an AI copilot – to reproduce it exactly is harder than just doing the flow yourself. The Chrome/Edge extension skips the description step entirely: install it, open the application you want to test, click Record, and walk through the flow the way a real user would. Every click, double click, right click, typed value (including in rich-text editors), selection, key press, drag and drop, scroll, and hover that opens a menu is captured as it happens, inside your real, already-authenticated browser session – including flows behind a login that a server-side scanner like CertiMind’s URL scan can’t reach on its own.

What Gets Captured, Not Just That Something Was Clicked

A raw click coordinate would make for a useless, unmaintainable test the moment the page layout shifts. The extension instead resolves each interaction against the live DOM as it happens and records the same kind of resilient, multi-attribute locator information CertiHeal’s recovery cascade already knows how to work with – so a recorded step is exactly as durable as a hand-authored one, not a shortcut that trades convenience for fragility.

Recording a Flow

• 1. Install the CertiQA Chrome/Edge extension (Manifest V3). During early access CertiQA provides it on request: contact [email protected].
• 2. In CertiQA open the test case and choose Record Steps (to capture one element, choose Pick from browser tab instead).
• 3. Open the application you want to test in another tab and walk through the flow normally – log in, fill forms, click through – exactly as a real user would. Recording carries on across page navigations and new tabs, and works inside iframes.
• 4. Choose Finish in the red bar on the page, or stop in CertiQA. The steps are already in your test case, as real, editable steps.

Passwords and Other Secrets

• The extension never reads what you type into a password, card or key-looking field. That step reads a Vault secret by name instead (for example PASSWORD, or API_KEY taken from the field’s name). CertiQA reminds you to create that secret in the project’s Vault before you run the test. Query strings and fragments in page addresses are not sent either.

Iframes, Self-Hosted CertiQA and Limits

• Steps inside an iframe are preceded by a Switch Frame step, and another switches back when you leave it. File inputs record the file name; set the path the runner should upload.
• Hover is recorded only when it opens something: a menu or panel opened by script, or a CSS hover menu when your next click is inside that menu item. Scrolling is recorded only when you cause it (wheel, trackpad, scroll keys, scrollbar), not when the page moves by itself. Plain mouse movement, text selection and touch gestures are not recorded; add those from the step picker.
• You record in Chrome or Edge. The tests you record run in any browser the runner supports.
• If your team runs CertiQA at its own address, add it on the extension’s Options page. Only addresses you add there can control the recorder.

One Thing to Check Before Trusting a Recording

• A recorded flow is a first draft, not a finished test – add explicit assertions wherever the recording only captured a click. The extension records what you did, not what you meant to verify.