Comments on: TDD does not mean Test First http://sarahtaraporewalla.com/thoughts/testing/tdd-does-not-mean-test-first/ Tue, 08 Jun 2010 10:50:32 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Ciprian http://sarahtaraporewalla.com/thoughts/testing/tdd-does-not-mean-test-first/comment-page-1/#comment-248 Ciprian Fri, 05 Dec 2008 12:31:26 +0000 http://sarahtaraporewalla.com/thoughts/?p=107#comment-248 Very well said! I enjoyed very much the conclusion! I had my own attempt to make a little light on this topic: http://mesterciprian.blogspot.com/2008/10/tdd-is-vague.html Very well said! I enjoyed very much the conclusion!
I had my own attempt to make a little light on this topic: http://mesterciprian.blogspot.com/2008/10/tdd-is-vague.html

]]> By: Damian http://sarahtaraporewalla.com/thoughts/testing/tdd-does-not-mean-test-first/comment-page-1/#comment-246 Damian Fri, 05 Dec 2008 01:18:14 +0000 http://sarahtaraporewalla.com/thoughts/?p=107#comment-246 One could argue that TDD doesn't lead to better code either. Still depends on who is doing the designing, people are not created equal. Writing tests first will usually help you to produce code that has less bugs and may help you produce a well designed system, but a test has nothing on a bit of experience, thought and intelligence. One could argue that TDD doesn’t lead to better code either. Still depends on who is doing the designing, people are not created equal. Writing tests first will usually help you to produce code that has less bugs and may help you produce a well designed system, but a test has nothing on a bit of experience, thought and intelligence.

]]> By: cremes http://sarahtaraporewalla.com/thoughts/testing/tdd-does-not-mean-test-first/comment-page-1/#comment-245 cremes Thu, 04 Dec 2008 23:32:34 +0000 http://sarahtaraporewalla.com/thoughts/?p=107#comment-245 I hope your next post explains (with examples) what a good test should look like. I've been playing with TDD now for about 10 months and am getting better at it, but I'm still far from perfect. Sometimes my tests are far too coupled to the underlying implementation rather than testing the behavior of an object (this is particularly true when mocking). Looking forward to your followup... I hope your next post explains (with examples) what a good test should look like. I’ve been playing with TDD now for about 10 months and am getting better at it, but I’m still far from perfect. Sometimes my tests are far too coupled to the underlying implementation rather than testing the behavior of an object (this is particularly true when mocking).

Looking forward to your followup…

]]>