Playwright specs that survive a redesign

Record once. Never test that flow by hand again.

Click through checkout the way a user would. QAZero stores a fingerprint for every element — not a CSS class — and emits a Playwright spec. When a developer renames a button, the spec re-binds. When you need proof it catches the bug, the RED gate runs it against the broken build first.

Built by the QA engineer behind test automation at Polymarket, upcover, Kinnect, and Brahma.

The problem

Your tests break more than your code does.

A developer renames a class and six specs go red. Someone spends the afternoon chasing selectors. None of that work caught a bug.

The flows that make money — checkout, onboarding, billing — are still clicked through by hand, because writing those specs is a week nobody has.

  • 01

    Stale locators

    Selectors go stale the sprint after you record them.

  • 02

    Called flaky

    “Flaky” is often a locator that pointed at yesterday’s DOM.

  • 03

    Checkout

    Checkout still has no spec because the last one rotted.

How it works

Three steps. You only do the first one.

  1. 01

    Record

    Add a script tag to staging, or load the Chrome extension. Click through the flow. Every step is a fingerprint (role, name, test id, structure, geometry) — not div.btn-primary.

  2. 02

    Spec

    QAZero emits a Playwright file plus a sidecar of ranked locators. You can download it. It is ordinary spec.ts. Nothing proprietary.

  3. 03

    Gate, then CI

    The RED gate runs the spec against a build where the bug still exists. Fail then pass is the proof. After that, the GitHub Action runs it on every PR. When the UI moves, healing re-binds the locator instead of going red.

Healing

The UI changed. The test continued.

Most heals never call a model. Cached locator, then a recorded alternate, then fingerprint similarity. Claude is last, and only if those miss.

qazero run — checkout.spec.tsChromium
Navigate to /productscached89ms
Click "Wireless Headphones"role+name220ms
Click "Add to Cart"fingerprint410ms
healed.btn-primarygetByRole('button', { name: 'Add to Cart' })
Navigate to cartlabel180ms
Assert: Cart shows 1 itemtext40ms
Results4 passed·1 healed·0 failed0.94s
  1. 01Free

    Cached locator

    Last run still matches. Fast. Most steps stop here.

  2. 02Free

    Recorded alternate

    Another locator from the original fingerprint matches uniquely.

  3. 03Free

    Fingerprint re-match

    Similarity against the live DOM — role, name, structure, geometry.

  4. 04Paid

    Claude

    Screenshot + DOM, only if the rest failed. The dashboard shows the cost.

Locator rank

  1. test id
  2. role + accessible name
  3. label
  4. placeholder
  5. alt / title / text
  6. role alone
  7. CSS (hashed classes rejected)
  8. XPath last

Ambiguity wins: a test id on five buttons loses to role+name on one.

Who it’s for

Built for teams that would rather ship than babysit a pipeline.

01

Startup CTOs

No dedicated QA. Record checkout once.

02

Engineering managers

Stop paying sprints to rewrite selectors.

03

QA leads

Automate the regression loop. Keep exploratory for yourself.

Why QAZero exists

I’ve built this system four times. This is the fifth — done right.

At four different startups — a DeFi prediction market, an insurtech, and two fast-moving product teams — I was the QA engineer. And at every single one, I ended up building the same thing from scratch: automated end-to-end tests, CI integration, and endless selector maintenance to keep them green.

Every company had the same problem. Every company needed the same solution. Nobody could buy it — so someone like me had to build it, badly, in the gaps between sprints.

QAZero is that system, productized: fingerprints instead of selectors, a RED gate so a spec has to prove it would have caught the bug, and healing that does not start with an LLM.

— Saswat Marpureddy, Founder

Pricing

Start with one flow, not a 20-person QA team.

Plans start at $500/month for your 5 most important flows. Month to month.

Launch

$500 / mo

Up to 5 critical flows, tested on every deploy and kept green. Cancel anytime.

  • Record with the snippet or Chrome extension
  • 5 flows covering your money path
  • RED gate against the unfixed build
  • GitHub Action on Chromium
  • Pilot: $500 for 2 weeks

Core

$1,200 / mo

Up to 12 flows. Same coverage, more surface area.

  • Everything in Launch
  • 12 flows across checkout and critical paths
  • Hosted runs on Browserbase
  • Priority support
  • Pilot: $1,000 for 2 weeks

Growth

$2,000 / mo

Up to 25 flows. Full suite for teams shipping fast.

  • Everything in Core
  • 25 flows across your product
  • Walkthroughs with the founder
  • Custom invoice available
  • Pilot: $1,500 for 2 weeks

More than 25 flows? We'll scope it on the call.

Annual prepay: 2 months free.

Comparison

You keep the specs. Healing is not a human sitting on the suite.

Not an AI QA agency. Not a hosted test cloud. A fingerprint, a RED gate, and ordinary Playwright files.

QAZero compared with writing specs yourself and QA Wolf
CapabilityQAZeroDoing it yourselfQA Wolf
You recordYes — snippet or extensionYou write every specThey staff writers
What you keepPlaywright in your repoYour repoTheir cloud
HealingFour tiers; AI lastManual rewritesHuman maintainers
Proof it catches the bugRED gateHopeTheir process
Lock-inSpecs are yoursNoneHigh

Walkthrough

Book a walkthrough

One recorded flow, on a call. Not a 48-hour AI audit of accessibility or performance. Pick a time, or email.

FAQ

Questions engineers actually ask.

What if the UI changes every sprint?

Healing tries the cached locator, then a recorded alternate, then fingerprint similarity. Claude only if those miss. The spec stays a Playwright file.

Who is behind this?

Saswat Marpureddy. Test automation at Polymarket, upcover, Kinnect, and Brahma. Same problem at every one: checkout tested by hand, selectors rotting.

Do we own the tests?

Yes. Download spec.ts. Run it with Playwright. The GitHub Action is this repo, not a black box.

How do we start?

Create a workspace at https://app.qazerolabs.com/sign-up, paste the snippet on staging, record one flow.

What does it cost?

Launch is $500/month for up to 5 flows. Core is $1,200/month for up to 12. Growth is $2,000/month for up to 25. Each plan has a 2-week pilot. More than 25 flows? We'll scope it on the call.

Is this Jam / English-to-test?

No. You click through the real UI. That is how the fingerprint exists.

Firefox / Safari / mobile?

Chromium today. Hosted runs use Browserbase. CI uses GitHub Actions.

Visual regression, a11y, performance?

Not this product. The job is a durable spec for a flow you already care about.