Test-Driven Development
Write the test first. Watch it fail. Write minimal code to pass.
The Iron Law
NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST
If you didn't watch the test fail, you don't know if it tests the right thing.
Write code before the test? Delete it. Start over.
When to Use
Always:
- New features
- Bug fixes
- Refactoring
- Behavior changes
Exceptions (ask first):
- Throwaway prototypes
- Generated code
- Configuration files
Thinking "skip TD
[Description truncada. Veja o README completo no GitHub.]