I was a bit of a late convert to the full test-driven development thing,
but I do have to say that it very quickly showed it's worth and IMHO
it's the only way to write any code of consequence (i.e. anything more
than a quick and dirty script for some specific task). I've lost count
of the number of times I've totally misunderstood a problem going in,
but managed to refine my understanding as I write some tests.
···
On Tue, 2006-10-17 at 23:15 +0900, Mark Woodward wrote:
Just as an aside I noticed you started with Unit Tests in the video. I
think I know the answer to this but I'll ask anyway. Should I do this for
*all* quizzes? ie is it a good habit to get into? Not unit testing per se
but building the test(s) *first*?
--
Ross Bamford - rosco@roscopeco.REMOVE.co.uk