Latest Articles:
- Heroic Failure on the 13th of November
- Ok, I'm not perfect and I still get angry - but still try to deal with it
- Tumbleweed Interview Candidates
- TDD is effective if you look at the right things
- Ballmer not the darling of the stock market
- For and Against Test-Driven Development
- Next life
- Rails authlogic: can't use OAuth and OpenID plugins together
Archive
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
March 2000
Tag Cloud:
Stats:
- Entries = 356
- Notes = 29
General Links
For and Against Test-Driven Development
I've been training people on TDD and the *first* thing I said is you need to start from the functional spec and then (maybe) create a technical spec that is used to drive the tests. Understand the problem first - and then the tests are just part of writing the code as a whole, no biggie.
Writing small tests for small bits of code make you think small, with short well focussed methods that *do* stuff. Long linear honkin' bits of procedural code are very hard to test properly. TDD has the accidental but very useful effect that you write stuff that isn't tightly coupled because it's impossible to do efficient TDD with tight coupling, assuming you get how to do it well. That takes practice. I think you should give it another try from the beginning with something simple and notice how the structure of your code is better (IMHO anyway).
When I'm doing demos or quick tracer bullet things then I don't bother, but then there are no consequences.
I agree that agilistas can be far too rigid - don't substitute process for thought. Anyone who ever suffered under RUP (or any big MC company's "method") knows how painful this is.
Testers test functionality. Programmers test assumptions. Not the same.