What is update-e2e-tests?

A command for bringing a project's end-to-end tests up to date with its E2E_TESTS.md specifications. End-to-end tests check complete user flows across the application.

Use it to discover test specifications and existing test files, analyze gaps, update the tests, and verify the result.

It helps find missing or inconsistent tests and align existing tests with the documented requirements. The description does not provide enough detail about the exact changes it makes.

How endorhq/rover configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to endorhq/rover. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/endorhq/rover/main/.claude/commands/update-e2e-tests.md

Clone the repo

git clone --depth 1 https://github.com/endorhq/rover

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/endorhq/rover/update-e2e-tests/github.svg)](https://agentmods.dev/commands/endorhq/rover/update-e2e-tests)

Your own site

<a href="https://agentmods.dev/commands/endorhq/rover/update-e2e-tests"><img src="https://agentmods.dev/badge/commands/endorhq/rover/update-e2e-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/endorhq/rover/update-e2e-tests"><img src="https://agentmods.dev/badge/commands/endorhq/rover/update-e2e-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,391 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01391
Opus 5.5	$0.00000	$0.00556
Sonnet 5.5	$0.00000	$0.00278
Haiku 4.5	$0.00000	$0.00139

Measured 2mo ago against content hash 19d2ffcb482c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-e2e-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/update-e2e-tests.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update E2E tests

Update the existing end-to-end (e2e) tests across the entire project to match the specifications described in the E2E_TESTS.md files. The user also requests the following instructions: "$ARGUMENTS". Ignore if empty.

This command has four phases:

Discover E2E specifications and existing tests
Analyze gaps and inconsistencies
Update tests
Verify

You must complete all four phases in order.

Phase: Discover E2E specifications and existing tests

Find all E2E_TESTS.md files in the project by searching recursively from the project root. Read the root-level docs/E2E_TESTS.md first to understand the overall testing philosophy, constraints, and execution methodology.
For each E2E_TESTS.md file found in a package directory, read it fully and extract:
- All test suites listed
- For each suite: preconditions, features, and postconditions
- Any constraints on test ordering, isolation, or shared state
Find all existing e2e test files in the project. Look for:
- Files matching **/*.e2e.test.ts
- Files inside **/e2e/**/*.test.ts directories
- E2e-specific Vitest/Jest configuration files (e.g., vitest.e2e.config.ts)
Read all existing e2e test files fully to understand the current test coverage, patterns, helper utilities, and mocking strategies in use.

Phase: Analyze gaps and inconsistencies

For each package that has an E2E_TESTS.md file:

Map each test suite and feature described in E2E_TESTS.md to existing test files and describe/it blocks. Build a coverage matrix:
- Which suites from the spec have corresponding test files?
- Which features within each suite have corresponding test cases?
- Which preconditions and postconditions are verified?
Identify:
- Missing suites: Test suites described in E2E_TESTS.md that have no corresponding test file
- Missing features: Features within a suite that have no corresponding test case
- Missing preconditions/postconditions: Setup or teardown that is described but not implemented
- Inconsistencies: Tests that exist but do not match the current spec (e.g., testing outdated behavior, wrong assertions, missing flags or options)
- Structural issues: Tests that violate the constraints from the root docs/E2E_TESTS.md (e.g., tests that depend on execution order, share persistent state between suites)

Read the full file on GitHub · 108 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 108 lines · 0 tokens per session scan A 19d2ffcb482c

Subscribe to this mod's changes

update-e2e-tests is a command published in the GitHub repository endorhq/rover (273 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,391 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

E2E testing Testing agentic-ai ai ai-agents claude codex gemini

update-e2e-tests next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-e2e-testsendorhq/rover	Command	273	7mo ago	Apache-2.0	A	0	Claude Code
implemententireio/cli	Command	5.3k	today	MIT	A	12	Claude Code
write-testsentireio/cli	Command	5.3k	today	MIT	A	11	Claude Code
triage-cientireio/cli	Command	5.3k	today	MIT	A	24	Claude Code
debugentireio/cli	Command	5.3k	today	MIT	A	12	Claude Code
distillnWave-ai/nWave	Command	631	yesterday	MIT	A	26	Claude Code
e2emodu-ai/moai-adk	Command	1.3k	3d ago	Apache-2.0	A	25	Claude Code

rover: Command for Claude Code