Comments on: Wrong About TDD http://blog.ontheheap.com/2008/10/30/wrong-about-tdd/ Doing things well in software development; by Stephen Rylander Wed, 06 Jan 2010 08:26:07 +0000 http://wordpress.com/ hourly 1 By: TDD-Einsichten « Stefan Roock http://blog.ontheheap.com/2008/10/30/wrong-about-tdd/#comment-59 TDD-Einsichten « Stefan Roock Thu, 19 Feb 2009 09:27:12 +0000 http://ontheheap.wordpress.com/?p=54#comment-59 [...] Siehe hier: http://blog.ontheheap.com/2008/10/30/wrong-about-tdd/ [...] [...] Siehe hier: http://blog.ontheheap.com/2008/10/30/wrong-about-tdd/ [...]

]]> By: Anthony http://blog.ontheheap.com/2008/10/30/wrong-about-tdd/#comment-41 Anthony Fri, 07 Nov 2008 01:38:19 +0000 http://ontheheap.wordpress.com/?p=54#comment-41 Agree, agree, agree. Whenever I heard "TDD" I thought unit tests and code coverage and would do these things post-implementation. My mind is bending around to the true meaning and am seeing all the advantages you have espoused. I am still not doing TDD religiously due to the "I don't have time" argument, but what I am doing is asking myself "how would I test this?" as I write my code. The result is, I am sure, not as good as if I did write my tests first, but it is resulting in better code than my usual brain to keyboard to editor chain with little processing in the flow. Actually, I think the real cause of my reticence in not doing TDD is that I am not suitably familiar with test tools and libraries and it is the learning of those tools that requires the upfront time investment. If I can get myself to a state where I can start a new project and with little effort have my test environment set and ready to go I am sure I would be head down hammering out those tests. Good post. Anthony. Agree, agree, agree. Whenever I heard “TDD” I thought unit tests and code coverage and would do these things post-implementation. My mind is bending around to the true meaning and am seeing all the advantages you have espoused.

I am still not doing TDD religiously due to the “I don’t have time” argument, but what I am doing is asking myself “how would I test this?” as I write my code. The result is, I am sure, not as good as if I did write my tests first, but it is resulting in better code than my usual brain to keyboard to editor chain with little processing in the flow.

Actually, I think the real cause of my reticence in not doing TDD is that I am not suitably familiar with test tools and libraries and it is the learning of those tools that requires the upfront time investment. If I can get myself to a state where I can start a new project and with little effort have my test environment set and ready to go I am sure I would be head down hammering out those tests.

Good post.

Anthony.

]]>