Build and keep end-to-end suites that are worth their runtime — which journeys belong at this level, selectors that survive refactors, waiting on state instead of sleeping, per-spec data isolation, and flake triage that finds the cause. Use when adding or repairing an e2e suite, when specs are slow or intermittently red, or when deciding whether a case belongs here at all. Not for one-off checking that a change renders, not for unit or integration tests, and not for load testing.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# End-to-end testing
The end-to-end level is the most expensive coverage available and the only level that can prove a
journey holds together. Suites die when those two facts are confused: everything gets tested here,
the suite gets slow and flaky, reruns become routine, and a red run stops meaning anything.
A suite whose failures are ignored is worse than no suite — it costs runtime and provides a false
signal.
## When this fires
Creating, extending, triaging or pruning an automated end-to-end suite. It does not fire for
manually confirming that a change renders and works (`browser-verification`), nor for coverage that
a unit or integration test could hold (`test-design`).
## Procedure
1. **Admit a journey only if it loses its meaning at a lower level.** Signup through first use;
add to cart through payment confirmation; a permission boundary spanning UI, API and database.
If a unit or integration test can observe the same failure, it belongs there — cheaper, faster,
and it names the cause instead of the symptom. Validation-message wording, per-field rules and
error formatting do not belong here.
…
The line at the top of this page pins the label git:20260919.a0d4f55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_7gnda45dgaxzhuew
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/e2e-testing
GET https://markdownregistry.com/api/v1/blob/7b9f519fa49eec6d32a0bed297153fbba94052fda3b4f8ad71c0e904be4f3b66
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Handle requested Agent Dispatcher work with direct execution or prepared specialist guidance. Includes named roles…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/model-routing/SKILL.md · Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
thedaviddias/front-end-checklist · skills/e2e-testing/SKILL.md · Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on…
qwenlm/qwen-code · .qwen/skills/e2e-testing/SKILL.md · Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic…
ericrisco/rsc-harness · skills/e2e-testing/SKILL.md · Use when writing or stabilizing Playwright tests that drive a real browser through multi-step journeys — durable…
billy-enrizky/openbrowser-ai · plugin/skills/e2e-testing/SKILL.md · Test web applications end-to-end by simulating user interactions and verifying expected outcomes.
Trigger when the user…
