Record how your product works, then replay it as a test
Walk through a feature once while the extension records the steps. Replay it any time — alone or with every other flow — and get a pass, a fail, or an honest “partly checked”, with a video split into chapters.
Your product's key journeys, checked by replay instead of by memory.
- Free to install
- On the Chrome Web Store
- Nothing is sent until you choose to
Hover to play
Sound familiar?
The problem
End-to-end test suites take engineering time to write, and the person who knows how the feature should behave is rarely the person who writes the test.
Writing end-to-end tests takes engineering time
So the critical journeys — sign-up, checkout — go untested until they break.
The person who knows the feature isn't the one writing tests
What “working” means gets lost between product and code.
“Did it pass?” comes with no evidence
A green tick nobody can replay is a claim, not a check.
What changes
Before and after Dr Urls — Capture
How it works
4 steps, start to finish
- 1
Record a walkthrough
Bind the panel to a tab and use the feature normally. Each navigation and step is captured and saved as a flow you can rename and edit.
- 2
Tag what it is for
Tags are instructions: a “mobile” flow is recorded at a phone-sized window, a “marketing-asset” flow switches the recorder on by default.
- 3
Replay one, or run them all
The extension replays the steps in your browser and records the screen as it goes.
- 4
Read the result
Each run is PASSED, FAILED or PARTIAL, step by step, with a video whose scrubber is split into chapters coloured by outcome.
What you get
- Flows written by doing, not by coding
- A result per step, with the screenshot it took
- A chaptered video of the run, with in and out points per step
- Flows a coding agent can be given as the definition of “working”
Who it's for
Product managers
Define what “working” means for a feature, without code.
QA
Replay every key journey before a release, with evidence.
Developers
Give your coding agent a concrete definition of done.
No surprises
Good to know
What it does not do, said up front.
- A step it cannot replay — a file upload, a drag — is recorded as skipped and turns the run PARTIAL. It never reports a pass it did not earn.
- “mobile” resizes the real window to trigger the site's breakpoints; it is not full device emulation.
- When a step leaves your site (a Google sign-in, say) the recording keeps rolling, but nothing off-site is clicked — the run waits until the tab is back.
FAQ
Questions
Do I need to write code?
No. You record by using the feature; the steps can be edited on the dashboard afterwards.
Can an AI write the flows?
Yes. Dr Urls can draft flows from your site, and Dr Urls Sync can map a codebase's features into flows with Claude Code. Both are saved as ordinary flows you can edit.
Where do the videos go?
Into the private storage bucket for your site, served only to people with access to it.
Also in the extensions
More you can do
Your product's key journeys, checked by replay instead of by memory.
Free to install. Your work goes to a free Dr Urls account, filed against the site it is about.
- Free to install
- On the Chrome Web Store
- Nothing is sent until you choose to