Documentation
Check whether Zerocheck fits your test flow
Zerocheck tests the web flows and expected outcomes your team describes. Start with a reachable environment, known test data and a result you can observe in the browser.
| Requirement | Current support |
|---|---|
| Desktop web testing | Chromium browser runs. |
| Plain-English authoring | Add one test or import a checklist; review, edit and save the steps. |
| Hosted execution | Run from the web app with no installation in your codebase. |
| Localhost and private networks | Use the CLI's local runner where your machine can reach the app. |
| Login | Configure login steps and named test credentials. |
| CI | CLI execution, JSON/JUnit reports and a generated GitHub Actions workflow. |
| Coding agents | Local stdio MCP server for compatible clients. |
| Explicit outcomes | Supported text, URL and network assertions; AI interpretation for other descriptions. |
| UI maintenance | Resolve moved equivalent controls and record evidence-gated healing. |
Flows that need a narrower test boundary
Email and SMS inbox actions, magic-link retrieval, native/mobile apps, API-only tests and canvas-only interactions are outside the current browser-step support. Browser-native login can work with supplied setup; a workflow that depends on retrieving a one-time code from an inbox needs additional preparation outside Zerocheck.
Zerocheck can interact with ordinary checkout pages using supplied test data. It does not supply a payment provider, test-card helper or guarantee that a production transaction is harmless. See test credentials and actions.
What a test result tells you
A passing test means its specified steps and expected outcomes passed in that run. It does not establish complete application coverage or diagnose every possible regression. A failed or incomplete run needs inspection of the test and its evidence.
The product does not crawl your app to discover a suite, infer tests from code changes, calculate a coverage/confidence score, or provide production incident alerts. Select the flows and test files that matter to your release.
Execution and editing limits
Tests run sequentially. The current product does not offer parallel sharding or additional browser engines. Each MCP process has one active browser job.
Tests created in the web app are edited there. Repository-managed tests are edited in YAML and are read-only in the web UI. Downloading a web test creates an independent copy; there is no automatic two-way repository synchronization.
Access and evaluation
Access is provisioned during assisted onboarding. The current instance model does not provide individual user accounts, SSO or role-based team administration. There is no per-seat charge for the Pilot, which describes pricing rather than separate user logins.
Try the flows you actually need during the free seven-day assisted evaluation. The continuing Pilot is US$500 per month for one project, with run cadence and usage agreed for your team.
Try your own customer flow.
Free seven-day assisted evaluation. No credit card.