# Zerocheck

> Zerocheck is an AI QA engineer that tests your app end to end. Verify critical flows and find bugs with a prompt.

Zerocheck is US$500 a month, with US$500 in credits at sign up. A dedicated instance for your team, with hands-on setup of your first tests. Run tests from the web app or CLI, with the screenshots and errors you need to investigate a failure. Each customer gets one dedicated instance, provisioned by hand during hands-on onboarding; there is no self-serve signup and no default public service.

Web-only teams need no repository or CLI installation: tests run in a hosted browser on the instance. The optional CLI is the npm package zerocheck. It runs repository YAML tests in Chromium on the user's machine or a CI runner, with the commands login, logout, whoami and run. The instance makes every decision and model call and keeps the results; the CLI drives the browser and holds test secret values, and it does not run offline. It has no MCP server, workflow generator, PR comment or JUnit report, and checklist import is web-only. Tests run in Chromium; login needs configured test credentials.

## When to use Zerocheck

- A team needs repeatable end-to-end tests for a web app and does not want to write or maintain selectors.
- The flows to check exist as a release checklist, or can be described in plain English with an expected outcome.
- Tests must run against a staging URL or production from the web app, or against localhost, a staging URL or production with the CLI.
- A coding agent should run saved repository tests with the CLI and read the exit code and JSON run record.
- Not a fit yet: native mobile apps, inbox verification, file uploads, popups, MFA, passkeys, social login, 3D Secure challenges, canvas-only interfaces and API-only tests. See [Supported flows and limits](https://tryzerocheck.com/docs/limits.md).

## Product and evaluation

- [How Zerocheck works](https://tryzerocheck.com/product.md): Zerocheck is an AI QA engineer that tests your app end to end. Verify critical flows and find bugs with a prompt. Run tests from the web app, your laptop or CI.
- [Pricing](https://tryzerocheck.com/pricing.md): Monthly price, usage, terms and Enterprise inquiries.
- [Book a setup call](https://tryzerocheck.com/onboarding/): Hands-on onboarding for your own app.

## Documentation

- [Start in the web app](https://tryzerocheck.com/docs/web-app.md): Describe a customer flow, draft and run a test, review the result, then save and run it in Zerocheck. No local installation required.
- [Import a QA checklist](https://tryzerocheck.com/docs/checklist.md): Import a release checklist, review one browser test per item, resolve missing details and save the tests your team wants to run.
- [Run locally with the CLI](https://tryzerocheck.com/docs/cli.md): Install the Zerocheck CLI and Chromium, sign in to your instance, and run repository YAML tests in a browser on your machine.
- [Run in CI](https://tryzerocheck.com/docs/github-actions.md): Run saved Zerocheck tests in a CI job you write, such as GitHub Actions, and use the CLI's exit code to enforce your merge policy.
- [Use a coding agent](https://tryzerocheck.com/docs/mcp.md): A coding agent edits YAML tests, runs them with the CLI, and reads the exit code and run record.
- [Test format and examples](https://tryzerocheck.com/docs/test-format.md): Zerocheck test fields, browser step syntax, explicit assertions, test-data placeholders and a complete example you can adapt.
- [Results, retries and healing](https://tryzerocheck.com/docs/results.md): Understand passed, failed and incomplete runs, step screenshots, visible retries, and the evidence required to save a healed target.
- [Credentials and data handling](https://tryzerocheck.com/docs/security.md): What your Zerocheck instance receives, how configured secrets are handled, when video is recorded, and how to prepare test accounts.
- [Supported flows and limits](https://tryzerocheck.com/docs/limits.md): Check whether Zerocheck fits your web app: Chromium, login setup, local and hosted access, supported assertions and current product limits.

## Guides

- [How to test Stripe checkout before release](https://tryzerocheck.com/guides/test-stripe-checkout.md): What to set up before testing a Stripe checkout, how a QA agent runs your purchase and decline checklist in a real browser, and what it leaves to your integration tests.
- [How to test a magic-link login flow](https://tryzerocheck.com/guides/test-magic-links.md): Break magic-link testing into the request form, email delivery, token handling and authenticated app state. Each part needs its own evidence.
- [How to test a SaaS onboarding flow](https://tryzerocheck.com/guides/test-onboarding-flow.md): Turn onboarding into independent browser tests with known account state and a visible definition of completion.
- [How to investigate flaky browser tests](https://tryzerocheck.com/guides/fix-flaky-tests.md): Start with the failing step, test data and observed outcome. Keep recovery visible instead of treating a retry as proof that nothing was wrong.
- [How to start browser testing without a QA team](https://tryzerocheck.com/guides/e2e-testing-without-qa.md): Use the release checklist your engineers already follow. Start with a small set of repeatable flows and make the expected outcomes explicit.
- [How to review browser test evidence](https://tryzerocheck.com/guides/soc2-testing-evidence.md): Keep the executed test, its environment and observed result together. Decide separately whether that record meets a particular review requirement.
- [How to evaluate AI test automation](https://tryzerocheck.com/guides/ai-test-automation.md): Use a real user flow to evaluate authoring, failure reporting and maintenance. A successful demo alone does not establish useful coverage.
- [How to write browser tests without test scripts](https://tryzerocheck.com/guides/no-code-e2e-testing.md): Describe the user’s action and expected result, then review the executable browser steps. No-code authoring still needs precise expectations and test data.
- [How to estimate browser testing costs](https://tryzerocheck.com/guides/e2e-testing-cost.md): Compare the cost of authoring, execution, maintenance and failure investigation using your own release cadence and flows.
- [How to fix flaky Playwright tests in CI](https://tryzerocheck.com/guides/fix-flaky-playwright-tests.md): Why Playwright tests pass locally and fail in CI: timing, shared data and runner differences, how to narrow down the cause, and what Zerocheck can and can't do alongside your suite.
- [How to investigate flaky Cypress tests](https://tryzerocheck.com/guides/fix-flaky-cypress-tests.md): Treat flaky end-to-end failures as evidence to investigate. Check state, waits and the expected outcome before changing the test framework.
- [What AI browser testing can take off your team’s plate](https://tryzerocheck.com/guides/replace-qa-team-ai.md): Automate repeated browser execution while keeping requirements, exploratory testing and release judgment with the people who know the product.
- [How a startup can build its first browser test suite](https://tryzerocheck.com/guides/e2e-testing-startups.md): Start with the customer journeys your team already checks by hand. Keep the suite small enough that every failure gets attention.
- [How to test authenticated browser flows](https://tryzerocheck.com/guides/test-oauth-sso.md): Separate identity-provider behavior from the app flows that require login. Validate the precise login setup before relying on automated browser tests.
- [How to choose an AI testing tool for a startup](https://tryzerocheck.com/guides/ai-testing-tools-startups.md): Shortlist tools by the work you need done: repeatable browser tests, broader device coverage or managed testing services.
- [How to share testing work without a dedicated QA team](https://tryzerocheck.com/guides/testing-without-qa-team.md): Make the release checklist explicit, automate repeatable browser flows and agree who owns failures before adding merge gates.
- [How to test changes written by coding agents](https://tryzerocheck.com/guides/vibe-coding-testing.md): Give the agent an expected user outcome, then verify that outcome in a real browser. Code generation and browser verification are separate steps.
- [How to add AI browser testing to an existing suite](https://tryzerocheck.com/guides/migrate-to-ai-testing.md): Start alongside the tests you trust. Evaluate a selected flow before changing ownership or replacing existing coverage.
- [How to run browser tests in GitHub Actions](https://tryzerocheck.com/guides/ci-cd-e2e-testing.md): Run saved browser tests against a known environment in a job you write, and make the merge policy explicit.

## Comparisons

- [Zerocheck vs Playwright](https://tryzerocheck.com/compare/playwright.md): Choose between a code-first browser suite and a service for turning a release checklist into editable browser tests.
- [Zerocheck vs Playwright MCP](https://tryzerocheck.com/compare/playwright-mcp.md): Compare Playwright MCP’s browser tools and opt-in verify tools for coding agents with Zerocheck’s saved, repeatable browser tests and run evidence.
- [Zerocheck vs Selenium](https://tryzerocheck.com/compare/selenium.md): Compare a browser automation ecosystem you assemble in code with a web app for drafting and running your release tests.
- [Zerocheck vs Cypress](https://tryzerocheck.com/compare/cypress.md): Cypress framework and Cypress Cloud pricing on 22 September 2026, compared with Zerocheck's QA agent: authoring, starting point, evidence and cost.
- [Zerocheck vs BrowserStack](https://tryzerocheck.com/compare/browserstack.md): BrowserStack addresses broad browser and device testing needs. Zerocheck focuses on repeatable browser tests drafted from your release checklist.
- [Zerocheck vs LambdaTest / TestMu AI](https://tryzerocheck.com/compare/lambdatest.md): LambdaTest now presents its offering as TestMu AI. Compare its testing cloud with Zerocheck’s focused browser-test workflow using your actual compatibility requirements.
- [Zerocheck vs Katalon](https://tryzerocheck.com/compare/katalon.md): Compare a broader quality platform with a focused way to turn a manual web-app checklist into browser tests.
- [Zerocheck vs Sauce Labs](https://tryzerocheck.com/compare/sauce-labs.md): Compare testing infrastructure for a broad platform matrix with a focused browser suite your team can author in plain English.
- [Zerocheck vs TestRail](https://tryzerocheck.com/compare/testrail.md): TestRail and Zerocheck solve different parts of the workflow: managing testing work and executing repeatable browser tests.
- [Zerocheck vs testRigor](https://tryzerocheck.com/compare/testrigor.md): Both offerings use natural-language test descriptions. Compare the exact flows, maintenance behavior and run evidence your team needs.
- [Zerocheck vs QA Wolf](https://tryzerocheck.com/compare/qa-wolf.md): Compare QA Wolf’s usage-priced platform and managed coverage service with Zerocheck’s assisted, team-authored browser tests. Pricing, ownership, flaky handling and platforms.
- [Zerocheck vs Octomind](https://tryzerocheck.com/compare/octomind.md): Compare AI-assisted browser testing on the same real user journey, including the failed path and the work needed to maintain it.
- [Zerocheck vs Rainforest QA](https://tryzerocheck.com/compare/rainforest-qa.md): Compare how each service turns your team’s testing knowledge into repeatable browser coverage, and who owns the ongoing work.
- [Zerocheck vs Checksum](https://tryzerocheck.com/compare/checksum.md): Compare a vendor’s test-generation workflow with Zerocheck’s explicit checklist-to-browser-test workflow.
- [Zerocheck vs e2e (TesterArmy)](https://tryzerocheck.com/compare/e2e.md): Compare TesterArmy's open-source e2e framework (TypeScript, bring your own model, web and mobile) with Zerocheck's assisted plain-English browser tests with evidence. Who writes the tests, first run, pricing and platforms.
- [Zerocheck vs Momentic](https://tryzerocheck.com/compare/momentic.md): Compare Momentic’s setup wizard and repository tests with Zerocheck’s assisted, web-first browser testing. See pricing, run evidence and supported platforms.
- [Zerocheck vs Autonoma](https://tryzerocheck.com/compare/autonoma.md): Compare Autonoma's codebase-generated suites on preview deploys with Zerocheck's QA agent for the flows your team describes. Setup requirements, evidence and pricing, dated.
- [Zerocheck vs Mabl](https://tryzerocheck.com/compare/mabl.md): Compare a broader agentic testing platform with Zerocheck’s focused workflow for repeatable web-app release tests.
- [Zerocheck vs QA.tech](https://tryzerocheck.com/compare/qa-tech.md): Compare what each testing agent actually runs, how you review its assertions and which supported platforms your application requires.
- [Zerocheck vs Tricentis Testim](https://tryzerocheck.com/compare/testim.md): Compare how each product creates, maintains and explains browser tests after your application changes.
- [Zerocheck vs In-house](https://tryzerocheck.com/compare/build-your-own.md): Compare building the exact test infrastructure your team wants with adopting a service for the browser checklist you already run.

## Glossary

- [What Is a Flaky Test?](https://tryzerocheck.com/glossary/flaky-test.md): A flaky test produces inconsistent results when the relevant code and expected behavior have not changed. Causes can include timing, shared state, infrastructure and external dependencies.
- [What Is E2E Testing?](https://tryzerocheck.com/glossary/e2e-testing.md): End-to-end testing verifies a complete user journey through an application. A browser E2E test performs user actions and asserts an outcome visible through the web app.
- [Self-Healing Tests: How They Work](https://tryzerocheck.com/glossary/self-healing-test.md): A self-healing test can recover a target after a UI change while preserving the original interaction and expected outcome. The category describes target maintenance, not permission to change the requirement.
- [What Is Test Flakiness?](https://tryzerocheck.com/glossary/test-flakiness.md): Test flakiness describes inconsistent results that do not correspond to a relevant change in the behavior under test. A flake rate is meaningful only when its measurement method is defined.
- [What Is Selector Brittleness?](https://tryzerocheck.com/glossary/selector-brittleness.md): Selector brittleness is the tendency of an element locator to fail after a UI implementation change even when the intended user behavior remains the same.
- [What Is Visual Testing?](https://tryzerocheck.com/glossary/visual-testing.md): Visual testing compares rendered appearance with an expected visual state. Depending on the tool, that may mean screenshot comparison, layout rules or human review.
- [What Is Test Maintenance?](https://tryzerocheck.com/glossary/test-maintenance.md): Test maintenance is the work of keeping test data, setup, actions and assertions aligned with the application’s intended behavior.
- [What Is PR Gating?](https://tryzerocheck.com/glossary/pr-gating.md): Pull-request gating prevents a change from merging until required conditions, such as a successful CI workflow, are met.
- [What Is Diff-Aware Testing?](https://tryzerocheck.com/glossary/diff-aware-testing.md): Diff-aware testing selects or proposes tests using information about a code change. It can use file mappings, dependency analysis or other signals; the exact mechanism depends on the tool.
- [What Is Agentic Testing?](https://tryzerocheck.com/glossary/agentic-testing.md): Agentic testing uses an AI agent to interpret a test objective and make decisions while interacting with an application. Scope varies: some tools draft tests, some execute them, and some propose exploratory tasks.
- [What Is a QA Agent?](https://tryzerocheck.com/glossary/qa-agent.md): A QA agent tests a running app the way a person would and records evidence for every step. What it does, what it needs from you, and ten questions to ask before you buy.
- [What Is Test Automation?](https://tryzerocheck.com/glossary/test-automation.md): Test automation uses software to execute defined tests and report observed results. Automated tests can target individual functions, service interactions or full user journeys.
- [What Is AI Testing?](https://tryzerocheck.com/glossary/ai-testing.md): AI testing can mean testing an AI system or using AI to help test software. In browser automation, it commonly describes AI-assisted authoring, target resolution or semantic assertions.
- [What Is No-Code Testing?](https://tryzerocheck.com/glossary/no-code-testing.md): No-code testing lets someone define tests without writing a conventional test program. It can use a visual editor, recorded actions or natural-language descriptions.
- [What Is Test Coverage?](https://tryzerocheck.com/glossary/test-coverage.md): Test coverage describes what a set of tests exercises. Code coverage measures executed code; behavioral coverage asks which user outcomes and edge cases have been tested.
- [What Is CI/CD Testing?](https://tryzerocheck.com/glossary/ci-cd-testing.md): CI/CD testing runs automated tests as part of integrating and delivering software changes. Different stages can execute different tests against suitable environments.
- [What Is Regression Testing?](https://tryzerocheck.com/glossary/regression-testing.md): Regression testing reruns tests to look for unintended changes in previously expected behavior after the application changes.
- [What Is Smoke Testing?](https://tryzerocheck.com/glossary/smoke-testing.md): Smoke testing runs a small set of high-value tests to determine whether the application is usable enough for further testing or release review.
- [What Is Compliance-Related Software Testing?](https://tryzerocheck.com/glossary/soc2-compliance-testing.md): Compliance-related testing is testing selected to support an organization’s own control and review requirements. A software test result alone does not certify compliance.
- [What Is Shift-Left Testing?](https://tryzerocheck.com/glossary/shift-left-testing.md): Shift-left testing means checking assumptions and behavior earlier in development, when changing an implementation is usually easier than after release.
- [What Is Continuous Testing?](https://tryzerocheck.com/glossary/continuous-testing.md): Continuous testing runs relevant tests throughout the delivery process so changes receive repeated feedback. The schedule and scope should match the team’s release decisions.
- [What Is Test Orchestration?](https://tryzerocheck.com/glossary/test-orchestration.md): Test orchestration coordinates which tests run, where they run, their required setup and how results affect a delivery process.
- [What Is Cross-Browser Testing?](https://tryzerocheck.com/glossary/cross-browser-testing.md): Cross-browser testing verifies an application in more than one browser engine or browser environment to identify compatibility differences.
- [What Is Test Data Management?](https://tryzerocheck.com/glossary/test-data-management.md): Test data management prepares and maintains the accounts, records and application state a test needs to run predictably.
- [What Is Codeless Test Automation?](https://tryzerocheck.com/glossary/codeless-test-automation.md): Codeless test automation expresses a test through an interface other than a conventional programming language, such as editable actions or natural-language steps.
- [What Is a Test Automation Framework?](https://tryzerocheck.com/glossary/test-automation-framework.md): A test automation framework provides conventions and tools for defining tests, preparing setup, executing assertions and reporting results.
- [What Is Autonomous Testing?](https://tryzerocheck.com/glossary/autonomous-testing.md): Autonomous testing is a broad term for systems that perform testing work with limited intervention. Vendors use it for different levels of planning, authoring, execution and maintenance.
- [What Is Test Automation Maintenance?](https://tryzerocheck.com/glossary/test-automation-maintenance.md): Test automation maintenance keeps automated tests useful as requirements, interfaces, environments and dependencies evolve.
- [What Is the Testing Pyramid?](https://tryzerocheck.com/glossary/testing-pyramid.md): The testing pyramid is a model for balancing many focused lower-level tests with fewer broad end-to-end tests. It emphasizes placing checks at a useful level rather than forcing every assertion through the UI.
- [What Is Functional Testing?](https://tryzerocheck.com/glossary/functional-testing.md): Functional testing verifies whether a system behaves according to a specified requirement, such as saving a setting or returning the expected search result.
- [What Are Test Automation Metrics?](https://tryzerocheck.com/glossary/test-automation-metrics.md): Test automation metrics describe the usefulness and operating cost of a test suite. Examples include feedback time, investigation effort, meaningful coverage and inconsistent results.

## Use cases

- [Release Checklist Automation](https://tryzerocheck.com/use-cases/release-checklist-automation.md): Paste your QA checklist. Zerocheck drafts editable browser tests, runs them in your app, and shows the result of each item before you save it.
- [Browser Run Evidence](https://tryzerocheck.com/use-cases/soc2-evidence.md): Zerocheck keeps the test, its step screenshots and its errors together, so an engineer can explain a browser test result.
- [Browser Tests in CI](https://tryzerocheck.com/use-cases/zero-to-ci.md): Start with a browser test in the web app, then use the optional CLI to run repository YAML in a CI job and act on its exit code.
- [Checkout Browser Testing](https://tryzerocheck.com/use-cases/checkout-testing.md): Turn your manual checkout checklist into browser tests. Check the actual success and decline outcomes in test mode, locally or hosted.
- [Email Flow Testing](https://tryzerocheck.com/use-cases/email-flow-testing.md): Test the sign-up, reset and confirmation pages around an email with a prepared account. Keep inbox and SMS checks in your integration tests.
- [Flaky Test Triage](https://tryzerocheck.com/use-cases/flaky-test-triage.md): Zerocheck shows the failing step, screenshots and console errors. A pass after a transient retry stays labelled flaky.
- [Testing Changed User Flows](https://tryzerocheck.com/use-cases/change-aware-testing.md): Use what a pull request changed to choose which browser tests to run. Your team picks the tests, and Zerocheck runs them.
- [Self-Healing Browser Tests](https://tryzerocheck.com/use-cases/transparent-self-healing.md): Spend less time maintaining tests when your UI changes. Zerocheck can recover from layout and selector changes, and shows you what changed in the run results.
- [Understanding Browser Test Results](https://tryzerocheck.com/use-cases/confidence-scoring.md): Zerocheck reports what each browser step did and whether the outcome you asked for passed, so your team can make the release call.
- [Prioritizing Revenue Flows](https://tryzerocheck.com/use-cases/revenue-flow-priority.md): Choose the user journeys that matter to your business, then turn them into browser tests. Your team sets the priority.
- [Testing Product Requirements](https://tryzerocheck.com/use-cases/test-to-spec-alignment.md): Describe what a user should do and what should happen. Zerocheck drafts the browser steps so you can compare the test with the requirement.
- [Reviewing Release Test Results](https://tryzerocheck.com/use-cases/for-compliance-teams.md): Zerocheck keeps each release test's steps, screenshots and result together, so an engineer can walk a reviewer through it. Your team decides what meets a compliance requirement.
- [Browser Testing for SaaS Teams](https://tryzerocheck.com/use-cases/for-growth-saas.md): Turn sign-in, onboarding, search and account-settings checklists into browser tests your team can review and run.
- [Browser Testing for Purchase Flows](https://tryzerocheck.com/use-cases/for-ecommerce-fintech.md): Repeat the customer-facing steps around products, carts and account pages with test data. Keep payment processing and provider-specific checks in a sandbox workflow.
- [Browser Tests and Production Monitoring](https://tryzerocheck.com/use-cases/production-monitoring.md): Zerocheck runs browser tests against the environments you configure, including production. Keep your existing monitoring for alerts and incidents.

## Examples

- [Examples](https://tryzerocheck.com/examples/README.md): project configuration, a release checklist to import in the web app, five saved tests (search, signup, test-card checkout, declined card, password reset) and an example GitHub Actions workflow.

## Agent resources

- [Agent instructions](https://tryzerocheck.com/agents.md): Product fit, authoring boundaries and CLI commands.
- [Agent authentication](https://tryzerocheck.com/auth.md): Device login, project tokens and what a token is used for.
- [Blog index for agents](https://tryzerocheck.com/blog/llms.txt): Dated index of posts.
- [Documentation index](https://tryzerocheck.com/docs/llms.txt): Individual task pages as Markdown.
- [Complete documentation](https://tryzerocheck.com/docs/llms-full.txt): All task references in one file.
- [Full product context](https://tryzerocheck.com/llms-full.txt): Offering, pricing, documentation and agent instructions.
- [HTML sitemap](https://tryzerocheck.com/sitemap/): Browse the rest of the website.

Updated: 2026-11-01