4 ms·
I've found TDD to be useful when you're implementing an interface outside your control, so the interface you test against is fixed and so are its semantics. Thi
by ygra 9y ago
I've found TDD to be useful when you're implementing an interface outside your control, so the interface you test against is fixed and so are its semantics. This basically means that the only thing in flux is the internal implementation, and it's easy coming up with a fairly complete set of tests beforehand.
In other cases I pretty much write my tests more or less randomly before, at the same time, or after the implementation.
- seanwilson 9y ago> In other cases I pretty much write my tests more or less randomly before, at the same time, or after the implementation. Similar most of the time. Once I know the interfaces have settled down and the problem you're solving is now well understood it feels like a better time to write tests. Once you have a feel for which parts are most error-prone as well you can concentrate on tests which have the most benefit.
- zxcmx 9y agoRight which is an interesting case because you're really doing TDV (test driven verification) against an existing design. Or ... testing.