rule-testing

Installation
SKILL.md

Testing

Testing Mindset

Coverage is a signal, not the goal. High-quality tests should increase confidence that the system can run safely in production under realistic, surprising, and failure-prone usage.

Do not stop at happy paths and basic parameter validation. Test the behavior users, clients, jobs, integrations, and future code changes are likely to stress after the service is deployed.

Good tests answer:

  • What must always be true in production?
  • What happens when this operation is repeated, retried, cancelled, or performed out of order?
  • What if valid data appears in an unusual state combination?
  • What if old data meets new code?
  • What if two actors perform related actions at the same time?
  • What if an external system is slow, stale, partial, duplicated, malformed, or unavailable?
  • What if the user has permission for one resource but not a related resource?
  • What side effects must happen exactly once?
  • What state must remain consistent after partial failure?
Installs
2
Repository
noih/dev-skills
First Seen
Apr 29, 2026