Prove a fix worked in a real browser before it ships
When a fix is ready, Dr Urls can ask your browser to replay the test flows attached to that task. You accept, it runs in its own window, and the task is closed only if the check passed.
A task is done when the fix has been checked in a real browser — not when someone says so.
- Free to install
- On the Chrome Web Store
- Nothing is sent until you choose to
Hover to play
Sound familiar?
The problem
A fix is usually “done” when someone says so. Nobody reopens the browser to check, so the same bug comes back as a new ticket.
“Fixed” on the ticket, still broken on the site
The same bug comes back as a new ticket, and the first one is already closed.
Nobody re-tests after the merge
Checking a fix by hand is the step everyone skips under pressure.
Automation that clicks anything is a risk
A script that can press “Delete” or “Pay” is not something you leave running.
What changes
Before and after Dr Urls — Capture
How it works
4 steps, start to finish
- 1
A task carries its check
Attach a test flow to the task — or let the fixing round draft one — so there is a definition of “it works”.
- 2
The fix asks for a replay
When the change is ready, a request appears in your side panel saying who is asking and why.
- 3
You accept, it runs
The flow replays in its own Chrome window so the page you were reading stays put, and every step is screenshotted.
- 4
Done means verified
A passing replay marks the task done. Anything less leaves it waiting for a person to review.
What you get
- A real-browser check on the exact flow that broke
- Screenshots of every step as evidence on the task
- Tasks that leave the queue only when the check passed
Who it's for
Engineering leads
Know a closed task was verified, not assumed.
Teams using coding agents
Make the agent prove its fix before the task closes.
QA
Spend your time on new checks, not re-running old ones.
No surprises
Good to know
What it does not do, said up front.
- It asks first. A flow a person recorded always waits for a person to accept; only checks the round wrote itself, made of look-and-click steps, may run on their own.
- Clicks that delete, pay, touch credentials, sign out or broadcast are refused, and so is any click that does not say what it targets.
- Only a FAILED run blocks. A run that was declined, timed out or only partly checked means “not checked”, never “broken”.
FAQ
Questions
Should I use my main account?
A separate test account is suggested, so a mistake in a flow can only reach test data. It is not required.
What starts these requests?
A fixing round running from the Dr Urls command line on a developer's machine. The browser never starts one; it only answers.
Also in the extensions
More you can do
A task is done when the fix has been checked in a real browser — not when someone says so.
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