testing
Installation
SKILL.md
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.