| name | pragmatic-testing |
|---|---|
| description | Decides whether to write a test, what it asserts, which test double it uses, and how many tests a change needs. Load before adding, changing, reviewing, or deleting any test or test double, when auditing existing tests for low value, and when proving that a test prune lost no protection. |
Tests exist so we can change the product and still ship it. A test that fails on every refactor and never catches a real bug makes change harder.