navigate
Page loads and route changes, with the URL
Chrome extension — QA Recorder v2.5.1
Click through it once.
Test it forever.
The recorder turns a real browser session into structured test cases - and grounds your generated automation scripts in selectors that actually exist.
Chrome recorder
Try it here — you are the test.
This little login page is live. Click around, type something, sign in — the recorder logs your real actions exactly like the QAMind Chrome extension does. Then convert your session into a test case.
Free / Chrome / v2.5.1 — records clicks, inputs, navigation and assertions from real sessions, captures each action exactly once with a verified Playwright locator, and imports everything into your workspace. A compact on-page panel shows the latest step and stays out of your way.
Sign in to Acme
00:00⌖acme-store.test/login
… waiting for you. Try the form ☝
What it captures
Four event types. Real values. Real selectors.
click
Every click captured exactly once — double clicks and forwarded label clicks are de-duplicated — with a verified Playwright locator plus CSS and relative XPath selectors
type
Typed values captured in plaintext for Assign steps — one step per value, not one per keystroke or blur
assert
Visible outcomes captured as assertions
New in v2.5.1
Cleaner captures. Locators that hold.
1
Plaintext Assign values
Record a BUG — snapshot the journey so far as a Defect recording without stopping; Stop & Download still saves the full Automation recording. Login and form flows now generate test cases with the actual typed email, username, or search text in the Assign input field — not [EMAIL] placeholders.
2
Stable name-attribute XPaths
Form fields prefer //input[@name='...'] over bogus label-for ids on Headless UI, Radix, and similar dynamic-id libraries.
3
Verified Playwright locators
Every captured element gets a locator picked by priority — getByTestId, getByRole with the accessible name, getByLabel, getByPlaceholder, then stable fallbacks — and each candidate is checked against the live page. Ambiguous matches are disambiguated with .nth(i), so generated scripts hit the element you actually touched.
4
One action, one event
Clicking Login twice, label-to-input forwarded clicks, and the duplicate input/change events browsers fire for a single typed value are all stored once. Dropdown picks and date selections are attributed to the right field — never a stale one.
Setup
Recording in four moves.
1
Install the extension
Free download, v2.5.1, unzip and load into Chrome or Edge. It sits quietly in the toolbar until you hit record.
2
Record a real session
Use your app like a person, not a script. The recorder timestamps every click, typed value, navigation and visible outcome — and the compact on-page panel shows the latest step as you go.
3
Stop - it lands in your workspace
The session appears in the Recordings inbox with a full event timeline, raw JSON view, and an AI preview of what it saw.
4
Generate cases and grounded scripts
One click drafts test cases from the recording. Attach it during script generation and the selectors come from your actual DOM — verified unique at capture time.
Your app already knows its test cases.
Record the flow you fixed last week - before it breaks again.