Decide what to test and at which level before any tests get written — enumerate failure modes by consequence, give each one the cheapest level that can actually observe it, and name what is deliberately left uncovered. Use when starting testing on a feature or a codebase, when asked for a test plan or why coverage sits where it does, or when a suite is large and still missing bugs. Not for writing the tests themselves, and not for proving a finished change works.
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
# Test strategy
Coverage percentage measures which lines ran, not which failures would be caught. A suite can be
90% green and blind to every way the system actually breaks, because tests get written where they
are easy to write — pure helpers, config objects, getters — and failures happen at boundaries.
This produces a short written allocation: risks, the level each is tested at, and what is not
tested. It does not produce tests.
## When this fires
Before writing a batch of tests, when planning a feature's coverage, when a suite is slow or
expensive and nobody can say what it buys, or after an escaped bug when the question is why nothing
caught it. It does not fire for adding one test to an existing pattern.
## Procedure
1. **Enumerate failure modes, not features.** For each one: what goes wrong, who notices, and what
it costs — corrupted data, money moved twice, a silent wrong number, a page that will not load,
a cosmetic slip. Rank by consequence times plausibility. A feature list produces even coverage;
a failure list produces useful coverage.
2. **Get the history before trusting your instincts.** Bug-fix commits, issue tracker, incident
…
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_vfvecppgjs2mrgcb
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/test-strategy
GET https://markdownregistry.com/api/v1/blob/2dc96fed8fecd79be2f02f82a430364eba0992630956818cf125a97eb321b5f2
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…
naodeng/awesome-qa-skills · skills/en/testing-types/test-strategy/SKILL.md · Use this skill when you need to define a test strategy covering scope, methods, resources, risks, and quality gates…
fishzjp/qa-skills · skills/test-strategy/SKILL.md · "How should this be tested?" Evidence-backed risk map → scope and depth across functional domains and 10 testing-type…
aethrox/doctrine · skills/test-strategy/SKILL.md · Suite-level testing decisions that sit above individual tests, where test data comes from (synthetic factories vs…
jpantsjoha/ai-native-developer-experience · skills/test-strategy/SKILL.md · Map requirement acceptance to proportionate executable checks and real user journeys before implementation and…
insideout-ai/make-it-work · evals/fixtures/multi-repo-workspace/ledger-api/claude-dir/skills/test-strategy/SKILL.md · Test strategy for `ledger-api`: where its tests live (including other repos), how to run them and what they need, where…
