go-test-effectiveness
Installation
SKILL.md
Go test effectiveness
Design tests that detect plausible defects and remain stable when irrelevant implementation details change. Treat coverage as reachability information, not proof of test quality.
A useful test has four parts:
- behavior worth protecting;
- a realistic defect that could violate it;
- an independent reason for the expected result;
- an assertion that fails when the defect is present.
Express each important test as:
This test protects [behavior] and fails if [defect] occurs.
If neither blank can be filled with a concrete answer, reconsider the test.