Tdd

by sentimony53d0630136d6MIT6 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

You MUST use this when implementing a behavior change - a feature, a bug fix, or a refactor whose contract is checkable - especially when a test could fail for a setup reason, assert the wrong boundary, pass without proving the requirement, or cross module, API, external, state, security, or visual boundaries. Not for purely mechanical edits with no observable behavior.

Instructions onlySoftware Development
  1. 53d0630136d6Currentcommit 53d0630Published Oct 8, 2026

Source and attribution

Source:sentimony/skillsinskills/tddat commit53d0630

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal