3 ms·
TDD will as often as not (and maybe even mostly) surface errors (or gaps) in the specifications rather than errors in the code.
by ams6110 9y ago
TDD will as often as not (and maybe even mostly) surface errors (or gaps) in the specifications rather than errors in the code.
- eropple 9y ago100%. This is perhaps one of its most powerful attributes. Whether I have a spec written on paper or one I've informally defined in my head, I very often find myself enumerating the potential failure cases (determining the domain and range of my code, as it were) and going "hey...wait a minute...what about X?". Writing tests after code is completed, on the other hand, lends itself to reifying an implementation as "correct" and divergence from the implementation as being wrong. No bueno.