test-design skillA
test-design is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Write unit and integration tests that fail for the right reason — behaviour-level assertions, boundary values, the smallest honest double, deterministic setup and teardown. Use when adding tests for new code, pinning a bug before fixing it, or repairing tests that stay green while the code is broken. Not for deciding what to test or at which level, not for browser journeys, and not a way to call a change verified..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Test design A test earns its keep only by failing when the behaviour it names is broken. Most bad tests are not wrong; they are inert — they assert on what the code does rather than what it must do, so they go red on every refactor and green through every real defect. Keep the verbs apart: **created** is the test file written; **executed** is a run that happened; **tested** is a check that will run again without you; **verified** is a conclusion about the system, and a passing unit test does not supply it. ## When this fires Adding coverage for new or changed code, pinning a reported bug before fixing it, or fixing a suite that passes while the behaviour is wrong. It does not fire for choosing which risks to cover at which level (`test-strategy`), nor for end-to-end journeys (`e2e-testing`). ## Procedure 1. **Name the behaviour in one sentence in the caller's terms** — "a refund over the original amount is rejected", not "calls validateAmount". If the sentence needs an internal name to make sense, you are about to test the implementation. 2. **Make it fail first, for the reason you expect.** New test: run it before the code exists or …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/test-design@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/test-design@sha256:37741f142d47e282Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_kcs62ug3mit4jqbi)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7682 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kcs62ug3mit4jqbi GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/test-design GET https://markdownregistry.com/api/v1/blob/37741f142d47e2829086126fac8e3e9d2154936a07249d9b9f105b21c5b90316
Your agent 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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher