Authoritative reference for deciding whether a test should exist and what it must assert. Use before writing or changing tests, and when investigating a test failure.
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
# Testing
This skill is the specialized, authoritative description of **why a test exists**: what deserves one, what it must assert, and what to do when it fails.
Follow the project's established conventions wherever they differ from these defaults. For code conventions and test execution, use the `engineering` skill when it is installed.
## Criteria
Answer these questions before writing a test. If any answer is missing, there is no test to write.
- **What promise does it protect?** State the behavior, contract, or rule in the domain's terms.
- **What regression would it catch?** Describe an incorrect change that would otherwise go unnoticed.
- **Would an equivalent implementation still pass?** A refactor must not invalidate the assertions when the promise is unchanged.
The test's name states the promise in the domain's terms, stays valid after a rename, and identifies what broke when it fails.
## What deserves a test
- **A behavior the product promises.** Cover rules that can be stated independently of the implementation, such as when an operation is allowed or how a failure is handled.
…
The line at the top of this page pins the label v1.0.1, 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_spsv2odseokijs5t
GET https://markdownregistry.com/api/v1/resolve?ref=wellwelwel/lagune/testing
GET https://markdownregistry.com/api/v1/blob/90d11c30a48c2801fd4dd4c84176bbf21d253eda9d088144d98d638fe6b6ccc3
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.
wellwelwel/lagune · .claude/skills/architecture/SKILL.md · Authoritative record of Lagune's architecture decisions, covering the three owners, what ships, the engine command, the…
wellwelwel/lagune · .claude/skills/blind-review/SKILL.md · Maps what a branch or the work in progress changes in behavior, before and after, from the code diff alone. Commit…
wellwelwel/lagune · .claude/skills/cdp/SKILL.md · Visual verification of a running page through Chrome's DevTools Protocol, capturing screenshots and measuring the…
wellwelwel/lagune · .claude/skills/dashboard/SKILL.md · Authoritative reference for the Lagune dashboard, a live view of a project's .lagune/ chain with a locked-down local…
wellwelwel/lagune · .claude/skills/ingest/SKILL.md · Use before reading any .txt file, whatever its name, and whenever a task builds on GitIngest digests. Checks whether a…
wellwelwel/lagune · .claude/skills/mcp-catalog/SKILL.md · Find, review, and add MCP servers to the reviewed catalog that lagune.ai serves to Lagune Code. Use when asked to look…
wellwelwel/lagune · .claude/skills/refine/SKILL.md · Confronts a scope with the engineering, testing, and writer skills, each where it applies, and with the architecture a…
wellwelwel/lagune · .claude/skills/simulate/SKILL.md · How to simulate a Lagune command end to end so the user sees both the process and the results in chat. Use when the…
wellwelwel/lagune · .claude/skills/specialize/SKILL.md · Author a new built-in Lagune specialization inside the Lagune source, not a project's own catalog. Use when adding or…
wellwelwel/lagune · .claude/skills/ui/SKILL.md · Design engineering principles for making interfaces feel polished. Use when building UI, reviewing frontend code, or…
wellwelwel/lagune · .claude/skills/writer/SKILL.md · Authoritative reference for writing the project's prose. Use before writing, editing, or translating any document…
davepoon/buildwithclaude · plugins/cc-best/skills/testing/SKILL.md · Testing strategies and methodologies including TDD, E2E testing, and multi-framework support
live-codes/livecodes · .agents/skills/livecodes/testing/SKILL.md · Write and run automated tests with Jest and Testing Library in the browser. Import code from script editor, use watch…
team-commonly/commonly · fleet-skills/testing/SKILL.md · Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or…
