CheckBefore merge
Discount accepted. Full price at checkout.
A shopper applies SPRING20 to a $100 order. “Discount applied” appears, but the total stays at $100 instead of $80.
Impact
Shoppers are asked to pay more than promised.
CLI 0.1.9 is out. Get started →
Free tier · hands-on onboarding →
Catch bugs before your users do.
Zerocheck is an AI QA engineer that tests your app end to end. Verify critical flows and find bugs before you ship.
Arni, the founder, sets up your E2E tests on the call. Free trial, then $500 a month.
zerocheck/tests/checkout.yaml
acme-shop
- zerocheck
- tests
- checkout.yaml
- signup.yaml
- billing.yaml
- invite.yaml
- .github/workflows
- zerocheck.yml
- release-checklist.md
- zerocheck.yaml
checkout.yaml signup.yaml zerocheck.yml
1version: zerocheck/v12name: Discount code reaches confirmation3blocks_merge: true4steps:5 - Navigate to /cart6 - Enter "SPRING20" in the discount field7 - Click Apply8 - Verify "Discount applied" is shown9 - Pay with the test card ${TEST_CARD}10 - Click Place order11 - Verify "Order confirmed" is shown
zerocheck(pull_request)Failing after 1m 21s
app.tryzerocheck.com/runs/run_8f3k2q
Check results
FailedDiscount code reaches confirmation
Environment staging · Browser local · Attempt 1 · Screenshots 7
- Navigate to /cart
- Enter "SPRING20" in the discount field
- Click Apply
- Verify "Discount applied" is shown
- Pay with the test card ${TEST_CARD}
- Click Place order
- Verify "Order confirmed" is shownPage showed "Payment declined"
staging.example.com/checkout
Acme Shop
Starter kit$129.00
Discount SPRING20 applied−$25.80
Total$103.20
Payment declined. Try another card.
Place order
Built for teams shipping with
Claude Code
Codex
GitHub Copilot
Cursor
Any of these sound familiar?
A new release breaks a critical flow, costing you trust and revenue.
Start with the journey that failed. Turn it into a saved test with an explicit expected outcome and run it before the next relevant change goes live.
See how to prioritize revenue flows →PRs pile up faster than your team can test, approve, and merge them.
Run the critical browser checks as part of releasing instead of another sign-off: the exit code gates the merge, with the evidence in the pull request.
See browser tests in CI →Verifying intended behavior is now your release bottleneck.
Describe the intended behavior once; every release is checked against it, with the evidence to show what changed.
See how to test product requirements →AI agents ship changes in minutes. Testing and verifying still takes hours.
Coding agents write more code than your team can check by hand. Selector-based test suites break on the first refactor, and each flaky failure sends an engineer to triage instead of to the next change.
Read how teams test without a QA team and run end-to-end tests without QA.
60-70%
of testing budget goes to maintaining brittle tests.
World Quality Report
No more manual QA or brittle test suites.
Zerocheck drafts, runs, and heals your end-to-end tests, so your team catches bugs without babysitting a test suite.
01
Write tests in plain English
zerocheck/tests/signup.yaml
version: zerocheck/v1 name: Signup creates a workspace blocks_merge: true steps: - Navigate to /signup - Enter "${EMAIL}" into the Email field - Click Create workspace - Verify "Welcome" is shown
Human-readable tests, kept in the web app or as YAML files in your codebase. No XPath or CSS selectors to maintain.
Learn more →02
Run locally and in CI
.github/workflows/zerocheck.yml
- run: npx zerocheck run --env staging - run: npx zerocheck report --file .zerocheck/latest-run.json if: always() ✓ zerocheck (pull_request) Successful in 1m 21s
Run anywhere with a single CLI command. Integrate with any pipeline that can run Node.js, gate every pull request, or run in a hosted browser from the web app.
Learn more →03
Import your test cases
zerocheck import
$ npx zerocheck import release-checklist.md Checklist import 7c1e4b: completed verified passing Signup creates a workspace verified passing Invite a teammate could not run Export invoices as CSV
Paste the checks your team does by hand, in the web app or with one command. Each item becomes a human-readable test with a real browser result. Start here if your checks already live in a document: no frameworks to learn, no scripts to maintain.
Learn more →04
Auto-heal as your product evolves
When a target moves, the test re-resolves it from the step's description and records the old target and the new one. A heal is saved only when the whole test passes with independent evidence; otherwise it stays pending. Real regressions remain failures.
Learn more →05
See why a test failed
A failed test shows the exact step, its screenshots, console errors and every attempt, in the web app, the CLI and one PR comment. A pass after a transient retry is marked flaky, never hidden.
Learn more →Bugs caught by Zerocheck
Catch them before they reach production. Nobody writes or maintains a script.
The QA agent for your web app.
Nothing to script. First tests running in just a couple of minutes. Your current release checklist can become your test suite.
01Describe a user flow and its expected result in plain English
~1 minDescribe a flow, or paste the release checklist your team clicks through by hand. Each item becomes a test you can read, in the web app or as YAML in your repo. No XPath or CSS selectors.
version: zerocheck/v1
name: Add Buy milk todo
blocks_merge: true
steps:
- Navigate to /todomvc/
- Enter "Buy milk" in the new todo field
- Press Enter
- Verify it appears in the list02Start a run locally or in CI
~1 minOne command on your laptop or in GitHub Actions, or run it in a hosted browser from the web app.
npx zerocheck run --env staging03Verify before you merge or deploy
every PRMake the tests a required check: a blocking failure exits non-zero and stops the merge, and the same tests run against staging or production before you deploy.
$ npx zerocheck run --env staging
FAIL Discount code reaches confirmation
exit 1: blocking failure, merge blocked
Arni Mittal
Founder, Zerocheck
Why I built Zerocheck.
I spent years watching the same pattern repeat across teams: add Playwright tests → a redesign breaks half of them → nobody fixes the selectors → tests get commented out → production breaks six weeks later. The tests failed because they depended on selectors that changed during redesigns.
Zerocheck starts from the checklist your team already trusts. Each item becomes a plain-English test with a real result. When the UI moves, the test finds the new target and shows you what changed. When the flow breaks, you get the failing step, not a green check.
Book a call and I’ll set up your first tests with you, on your app.
You’re already paying for app testing
CI passes, but code alone does not prove the app works.
Unit tests catch code issues. They miss a broken checkout, or a CSS change that hides the buy button. The manual click-through your team still does is the QA run Zerocheck automates.
Playwright still needs setup and maintenance.
Someone has to wire it into CI, write the selectors, and fix them every time the UI changes.
“Won’t AI-run tests flake in CI?”
Navigation, key presses, URL checks, quoted-text checks and targets a passing run already proved run without a model. The AI finds targets that aren’t proven yet and judges plain-English Verify steps; it never clicks. A transient error is retried once in the same browser, and a pass after that is labeled flaky. Assertion failures are never retried.
“Can’t I just use Playwright MCP with Claude Code?”
Playwright MCP gives your coding agent a browser. Zerocheck gives it a test suite: the same MCP server writes and runs tests from coding agents such as Claude Code or Cursor, runs them in CI, and posts results to the PR.