Software Development
Test Driven Development
Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.
- Publisher / source
- cbrock84/headcount (found on the CSV list)
- Upstream record
- cbrock84/headcount
- Version
- Version 2
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-03
- Content fingerprint
11c5bb96274ff6daa521ca25ce87ef1fe1e046a83a6865f1dac37a9ca58c8b62