Skip to main content
New: 189 SEO checks now available. See what's new
VS Code extension · AI-written test flows

Get a test flow for every feature without recording one

Dr Urls drafts test flows from what it knows about your site — its pages, your recent captures, the latest audit — and Claude Code can map every feature straight from your codebase. Each draft is an ordinary flow you review, edit and replay.

A first map of your product's features, as flows you can replay.

  • Free to install
  • VS Code Marketplace & Open VSX
  • Sign in from the browser — no key to copy

Hover to play

Sound familiar?

The problem

Recording a flow for every feature is still work, and the features nobody thought to record are exactly the ones that break unnoticed.

Nobody has a list of everything the product does

So nobody can say which features are covered by a check and which are not.

Recording every flow by hand is still work

The features nobody thought to record are the ones that break unnoticed.

Generic checklists don't fit your product

“Test the login” tells you nothing about your settings screen or your export.

What changes

Before and after Dr Urls Sync

Without it
With Dr Urls Sync
No inventory of features, or one that is out of date
Draft flows proposed from your real pages, captures and audit
Flows recorded one at a time, when someone has time
Claude Code maps features straight from the codebase
Generic test ideas copied from a template
Every draft reviewed and activated by a person before it runs

How it works

4 steps, start to finish

  1. 1

    Draft from the site

    On the dashboard, generate flows for a site: the AI reads its crawled pages, titles and headings, a few recent captures and the latest audit, and proposes one flow per feature it can identify.

  2. 2

    Or map it from the code

    In VS Code, “Map all features (Claude Code)” and “Generate test flows” let Claude Code read the codebase itself and add flows for the features it finds.

  3. 3

    Review the drafts

    Every generated flow arrives as a draft. Rename it, fix a step, tag what it is for, then turn it on.

  4. 4

    Replay them in Chrome

    From there they are ordinary flows: replay one, run them all, attach them to a task as its definition of “working”.

What you get

  • A first map of your product's features as runnable flows
  • Flows drawn from the real pages and the real code, not a generic checklist
  • Drafts you control: nothing runs until a person turns it on

Who it's for

  • Founders & small teams

    Get coverage of the whole product without a QA hire.

  • Developers

    Let Claude Code map the features it can read in the code.

  • QA

    Start from a draft for every feature, then refine.

No surprises

Good to know

What it does not do, said up front.

  • Drafting from the site spends credits, at the rate shown on the pricing page, and needs an audited site to read.
  • The site-based draft sees pages, captures and the audit — not your code. The codebase mapping needs Claude Code and Dr Urls Sync.
  • A draft is a starting point: steps that need real data (a login, a card number) are left for you to fill in.

FAQ

Questions

Do generated flows run by themselves?

No. They are drafts until someone reviews and activates them, and replaying them happens in your Chrome like any other flow.

Which should I use — the site or the code?

The site-based draft needs nothing installed and covers what a visitor can reach. The codebase mapping finds features behind sign-in and settings screens that the site alone does not reveal.

A first map of your product's features, as flows you can replay.

Free to install. Your work goes to a free Dr Urls account, filed against the site it is about.

  • Free to install
  • VS Code Marketplace & Open VSX
  • Sign in from the browser — no key to copy