Hey nickpsecurity! :) > I don't see TDD as either strongest method or state of the art. It's not the strongest method. But as far as the SWEBOK[0] is concerne

Hey nickpsecurity! :) > I don't see TDD as either strongest method or state of the art. It's not the strongest method. But as far as the SWEBOK[0] is concerned it is state of the art. The most effective teams I've worked with layer their testing strategies and use multiple approaches to verification depending on the needs of the project. I love quickcheck. I even pull out formal methods when the problem domain demands it or I need to check my thinking. On the scale of "sketch on a napkin" to "verified and signed-off-by-master-engineer blueprint" I'd say a unit test suite, as far as it is a specification, is somewhere between napkin and the middle. If you use a soundly typed language AND a unit test suite using property-based assertions you're somewhere in the middle; building houses. However I do see it as a warning sign if a team actively avoids TDD and tries to ship the first thing that works. If I was an actuary that project would represent a high level of risk and I'd probably raise their insurance rates to match that risk depending on the work they're trying to do.