Updated 7 October 2026

Zerocheck vs e2e (TesterArmy)

e2e is TesterArmy's open-source TypeScript testing framework, launched on 2 October 2026: agent steps and deterministic assertions in the same test, bring your own model, web and mobile. Zerocheck is an assisted product for teams that do not want to write a test suite: describe the flow or import the release checklist, review the browser result, and save the tests you want to run.

Book a setup call

What e2e (TesterArmy) does well

•Fully open source under Apache-2.0, and the first run costs nothing: npx e2e init writes a config and an example test, and npx e2e run passes with no model, no sign-in and no API key. Four days after launch the npm package had about 60,000 weekly downloads.
•One test mixes agent.act, agent.assert and agent.extract with Playwright-style locators and assertions. An agent step that a later assertion verifies is recorded, and later runs replay it without model calls until the app changes, which keeps token spend down.
•Bring your own model with no markup: a ChatGPT, GitHub Copilot, SuperGrok or OpenCode subscription, any API key, a gateway, or a local model. Web on Chromium, Firefox and WebKit; iOS simulators and Android emulators through agent-device; hosted browsers from Kernel and hosted simulators from Expo as optional targets.
•Built for coding agents: one paste prompt sets it up from Claude Code, Codex or Cursor, the package ships a skill, MCP configuration and its docs inside node_modules, and there are migration guides from Playwright, Cypress, Selenium, Detox and Maestro plus a pull-request comment reporter.

What to evaluate with e2e (TesterArmy)

—It is a framework, not a service. Your engineers write and maintain .e2e.ts files in TypeScript, pick and pay for a model, and run the infrastructure or hosted targets themselves. TesterArmy's hosted platform is a separate product that uses e2e as its foundation.
—It is pre-1.0. The README says APIs and configuration can still change between minor releases, so a suite written this month may need edits as the framework settles.
—Decide who confirms the expected outcome. agent.assert judges the screen with a model, and only agent steps backed by a later deterministic assertion are cached for replay; a product manager with a release checklist still needs an engineer to turn each item into code.

How Zerocheck differs

No test code. Describe a flow in plain English or import the release checklist; Zerocheck drafts each test, runs it in a real browser, and shows the result before you save it. Tests are readable YAML you own, in the web app or in your repository.
Each run keeps step screenshots, console errors and the steps that ran, in the web app, with a results link from the CLI. A pass after a transient retry stays labeled flaky, and a failed expected outcome is never retried into a pass.
Runs against your real environments with configured test credentials: from the web app in a hosted browser, or with the CLI on your machine or a CI runner, which a coding agent can also run. Hands-on onboarding on a dedicated instance; the CLI's source is public, but the instance is not open source; Chromium web only; your instance makes every decision and model call.

Side-by-side

e2e (TesterArmy) and Zerocheck: workflow and capabilities
Feature	e2e (TesterArmy)	Zerocheck
Model	Open-source framework; bring your own model and infrastructure	Assisted product: your team describes and reviews, Zerocheck runs and keeps the evidence
Who writes the tests	Your engineers, in TypeScript	Your team, in plain English or by importing a checklist; drafts reviewed before saving
Test format	.e2e.ts files mixing agent steps and Playwright-style locators	Plain-English YAML, editable and downloadable
First run	npx e2e init, then npx e2e run; no account or model needed	Web app or CLI after a setup call provisions your instance
AI model	Your subscription, API key, gateway or local model; no markup	Your instance makes the model calls, included in your run allowance
Platforms	Chromium, Firefox, WebKit; iOS simulators and Android emulators	Chromium web browsers
Evidence	Failure pages under .e2e with the failing step, screenshot, trace and logs	Step screenshots, console errors, every attempt and revision, on your instance
Pricing	Free (Apache-2.0); model and hosted targets billed by their providers	US$500 in credits at sign up, then US$500/month with a dedicated instance and hands-on onboarding

Sources: tester-army/e2e on GitHub; e2e on npm; e2e quickstart; Launch post. Reviewed 7 October 2026.

FAQ

Is e2e by TesterArmy free?

Yes. The framework is open source under Apache-2.0 and the first run needs no model, sign-in or API key. Agent steps use a model you supply: a ChatGPT, GitHub Copilot, SuperGrok or OpenCode subscription, an API key or a local model, billed by that provider, and hosted browsers or simulators from Kernel or Expo are billed by them. Zerocheck is US$500 per month, with US$500 in credits at sign up, for one project on a dedicated instance, with hands-on onboarding.

Do I need to write TypeScript to use e2e?

Yes. Tests are .e2e.ts files that import test and expect from e2e, call agent.act and agent.assert for the agentic steps, and use Playwright-style locators and assertions for the deterministic ones. Zerocheck tests are plain-English YAML drafted from a description or an imported checklist and reviewed in the web app before saving.

Can a team use both?

Yes, for different jobs. Engineers who want a code-first suite with their own model can keep it in e2e. The release checklist the rest of the team checks by hand before a release can run in Zerocheck with evidence on your instance. Zerocheck does not run e2e tests and does not export them.

Try it on your own app

US$500 in credits at sign up, with a dedicated instance and hands-on onboarding.