testing-strategy skillA
testing-strategy is agent-read markdown (skill) from drafthq/draft: Design test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD..
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
# Testing Strategy You are designing a testing strategy and test plan for this project or track. ## Red Flags — STOP if you're - Writing a strategy without understanding the codebase - Setting unrealistic coverage targets (100% is rarely appropriate) - Focusing only on unit tests and ignoring integration/E2E - Ignoring existing test infrastructure and conventions - Not considering the testing pyramid for this project's architecture **A good testing strategy matches the architecture. Not every project needs the same pyramid.** --- ## Pre-Check ### 0. Capture Git Context Before starting, capture the current git state: ```bash git branch --show-current # Current branch name git rev-parse --short HEAD # Current commit hash ``` Store this for the report header. The strategy is scoped to this specific branch/commit. ### 1. Verify Draft Context ```bash ls draft/ 2>/dev/null ``` If `draft/` doesn't exist, this skill can still run standalone with reduced context. ### 2. Load Draft Context (if available) Read and follow the base procedure in `core/shared/draft-context-loading.md`. ## Step 1: Parse Arguments …
Read the whole file at its exact version.
How to install
mdr add drafthq/draft/testing-strategy@git:20260819.fda278emdr add drafthq/draft/testing-strategy@sha256:e78a17ad9bac5be0Pin 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_ikaqvybo7lrzgmss)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.fda278e latest | 2026-08-19 | fda278e | 7,333 B | A | view · diff |
| git:20260517.6abc798 | 2026-05-17 | 6abc798 | 7,322 B | A | view · diff |
| git:20260510.83cfec7 | 2026-05-10 | 83cfec7 | 7,479 B | A | view · diff |
| git:20260510.63773a1 | 2026-05-10 | 63773a1 | 7,326 B | A | view · diff |
| git:20260426.17a2037 | 2026-04-26 | 17a2037 | 7,337 B | A | view |
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 (7333 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
drafthq/draft · 40 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ikaqvybo7lrzgmss GET https://markdownregistry.com/api/v1/resolve?ref=drafthq/draft/testing-strategy GET https://markdownregistry.com/api/v1/blob/e78a17ad9bac5be004d01fcedf68d715b6d3ad95ce86f812e49133e6ba15e55b
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.