Specnote
Get started
AI test automation

Don't know what you built? Neither do your tests.

AI says "all tests passed" and errors still show upbecause those tests were written without knowing what was built.

01Confirm what was developedA person confirms the list AI submitted
Developed this roundall 5 confirmed

AI submitted this list. Only a person can confirm it.

01Card registration on checkoutPasses when Saved card shows up in the list
02Date picker for meeting bookingPasses when Booking lands on the chosen date
03Drag to reorder tasksPasses when New order survives a refresh
04Search customers by namePasses when Partial name still returns results
05New notification settings screenPasses when Muted alerts stop arriving
Confirmed — only this scope gets tested
02Only the confirmed scope is testedA real browser clicks through it and leaves a recording
shop.io / checkout6 / 10 passedLIVE

Checkout

Shipping

Name

Address

Payment

Card number

Expiry

CVC

Subtotal$89.00
Shipping$3.00
Total$92.00
Enter shippingEnter paymentClick payConfirm

AI called itall passed.

The breakage was still there.

"Just tell Claude Code to test it, right?"

AI did not get it wrong.It understood it differently.

A short request leaves room, and AI builds on its own reading.That reading can be reasonable and still differ from what you pictured.

What you requested

“Show sold out when stock runs out”

What you pictured: and block the purchase

The screen you pictured
StoreSOLD OUTWireless earbuds$89.00Out of stockOut of stock
Cannot be bought
The screen AI built
StoreSOLD OUTWireless earbuds$89.00Out of stockBuy now
Still buyable
Orders keep coming in for stock that is not thereWhat AI verifiedTestedWhether the sold-out badge appearsVerdictPass

AI built what it understood, and verified exactly that.Whether it matched what you pictured, nobody looked.

Check the list of what AI built first, and this gap gets caught before any test runs

FIG.02HOW IT WORKS

Confirm, test, and get the result

01

Confirm what was developed

AI lists what it developed this round. Skim it, drop what is wrong, add what is missing.

specnote.io / my workspaceLIVE
01Confirm what was developed
Developed this round4 items
Welcome email on signupPasses when The email arrives after signing up
Password reset link expiryPasses when An expired link prompts a new request
Profile photo uploadPasses when The uploaded photo appears at once
New notification settingsPasses when Muted alerts stop arriving
02

Test the confirmed scope

A real browser clicks through those items in order. Green for pass, red for fail.

specnote.io / my workspaceLIVE
02Test the confirmed scope
Actual recording

Straight from the replay — AI typed the credentials and clicked through itself.

03

On failure you get a video and a report

See where it stopped on video, with the cause and the fix written up. Hand it to your AI and the fix begins.

specnote.io / my workspaceLIVE
03On failure you get a video and a report
Cancel paymentFailed
The moment of failure is kept on videoSteps runSign inOpen payment historyClick cancelConfirm the dialog
Passes whenThe cancel dialog opensWhat happenedClicking the button changed nothing on screenSuggestion: check the handler wired to the cancel button.
Copy report for your AI

Same pass, different outcome

Both said passed.What counted as passing differed.

Same items, same count. The only difference is where the bar sits.

Criteria AI setPassed 4 / 4
  • Passes if the sold-out badge shows
  • Passes if the email is sent on signup
  • Passes if it expires after 24 hours
  • Passes if the photo appears in the list
Built differently than you picturedIt said passed, and still became a problem
Criteria you correctedPassed 4 / 4
  • Passes if buying is blocked toocorrected
  • Passes only after the address is verifiedcorrected
  • Passes if it expires once usedcorrected
  • Passes if the photo appears in the list
Built the way you picturedPassing actually meant nothing was wrong

Not because the tests ran better.Because a person set what passing means first.

MCP CONNECT

One MCP line to connect,then a single sentence.

One MCP line in a config file finishes the setup. After that you just talk to the AI you already use.

Say this to your AI

“Run tests on what I developed this round”

Right awayWhat was developed lands in Specnote as a list to confirm

Confirming and running happens in Specnote from there.

How it connects

Your AI toolSpecnoteYour service

One MCP line in config · 1-minute setup

Connect GitHub and changed code carries over on its own

If it runs on the web, it worksNext.jsReactVueSvelteAstroRemixHTML/JSSupported nowReact NativeFlutterComing soon

Any service that opens in a browser can be verified, regardless of framework.

FIG.06PRICING

Start free

Scenarios are unlimited — credits only when you verify.

FreeBuilding solo
$0/mo
  • 1 workspace
  • Unlimited scenarios
  • Free verifications every month
Start free
Most popular
StandardFor individuals & small teams
$39/mo
  • Unlimited scenarios
  • 260 credits every month
  • AI interviews & auto extraction
Start Standard
ProVerifying every day
$99/mo
  • 660 credits every month
  • Priority AI processing
  • Priority support — replies within 24h
Start with Pro
Frequently asked questions

Code access is read-only, and sensitive values like passwords and API keys are automatically masked at collection.

Now a pass means
you can ship on it.

30 seconds to sign up · 5 minutes to your first test

Start testing free