e2e

e2e is an open source end-to-end testing framework for web and mobile apps. A test mixes agent goals (agent.act) with exact locator steps and assertions, and runs in a browser or on an iOS simulator, Android emulator, or phone.

Skills

• e2e: set up e2e in a project, write and fix tests, run them, debug a failed run, drive the running app over the e2e MCP server, explore an app toward a goal, and bug bash a branch with each bug proven by a repro test.
• create-verification-skill: generate a project-local verify-<app> skill and feature map on top of e2e. Invoke it with /e2e:create-verification-skill in Claude Code or $e2e:create-verification-skill in Codex. It loads only when invoked.
• migrate-to-e2e: port a Playwright, Cypress, Selenium, Detox, or Maestro suite to e2e one slice at a time, with the old suite running beside the new one and a MIGRATION.md file the next session resumes from.

Install

The tester-army/e2e repository is a marketplace for both clients. Both marketplace files point to plugins/e2e, and installation copies this directory into the client's cache.

Claude Code:

claude plugin marketplace add tester-army/e2e
claude plugin install e2e@e2e

Codex:

codex plugin marketplace add tester-army/e2e
codex plugin add e2e@e2e

Start a new session after installing. The plugin's version follows e2e releases. Update it with claude plugin marketplace update e2e followed by claude plugin update e2e@e2e, or in Codex with codex plugin marketplace upgrade e2e, then start a new session.

To try local changes, run the same commands from the monorepo root with ./ in place of tester-army/e2e. Claude Code reads a local marketplace in place, so edits show at the next session start or /reload-plugins. For a one-session Claude preview, run claude --plugin-dir ./plugins/e2e.

The plugin is not listed in either client's public directory.

Requirements

Node.js 24.8 or newer, or 22.22.3 or newer on Node.js 22. In a project that does not use e2e yet, the skill asks before setting it up. Agent steps need a model: an AI SDK provider key, or a ChatGPT subscription through npx e2e login openai.

MCP server

The plugin does not bundle the e2e MCP server, which runs from the project's own e2e install. To let Codex drive the running app, add it to the project's .codex/config.toml:

[mcp_servers.e2e]
command = "npx"
args = ["e2e", "mcp"]

For Claude Code, run this from the project to test:

claude mcp add --scope project e2e -- npx e2e mcp

Writing and running tests through the CLI does not require an MCP connection.

Data

• The e2e CLI sends anonymous usage telemetry (commands, engines, versions, failure codes; never test content, app content, or credentials) to a PostHog project run by the e2e maintainers. Turn it off with E2E_TELEMETRY_DISABLED=1, DO_NOT_TRACK=1, or npx e2e telemetry disable. See Telemetry.
• npx e2e feedback sends a report to the same project. The skill shows the report first and sends it only when you agree.
• Agent steps send the redacted screen to the model provider you configure. See Security for what is redacted.

Maintain the package

Edit skill Markdown in the monorepo's skills/ directory, then run pnpm plugins:sync. Commit the generated copies with the source changes. pnpm plugins:check, also part of pnpm check and CI, catches drift.

The Codex manifest owns the plugin's metadata. The sync command generates the Claude manifest from it and copies the root license. Skill UI metadata in skills/*/agents/openai.yaml and the plugin's assets are maintained here. Keep every referenced file inside this plugin directory so cached installs work without the rest of the monorepo. The repo's development .mcp.json is outside this package.

The initial Codex manifest, icons, and skill UI metadata came from tester-army/plugins at 9954005. The shared skill content follows this monorepo's current sources. Docs: https://e2e.tester.army/docs.