Comments on: Tod Golding on TDD http://blackbeanbag.net/wp/2006/10/04/tod-golding-on-tdd/ Thoughts on software development and other stuff Sat, 20 Jul 2013 01:54:41 +0000 hourly 1 https://wordpress.org/?v=3.9.40 By: pperalta [Member] http://blackbeanbag.net/wp/2006/10/04/tod-golding-on-tdd/comment-page-1/#comment-10 Thu, 05 Oct 2006 13:24:38 +0000 http://blackbeanbag.net/wp/?p=20#comment-10 I think it means that we should give more care to the test suite. Obviously you won’t use TDD for the tests themselves, but it does mean refactoring out duplication, using inheritance and polymorphism where it makes sense, etc. The main idea is to not allow the tests to become a hindrance to change.

As mentioned before, I’m guilty of copy-and-paste code, magic numbers, etc in my test cases, so this will be a bit of a transition for me. I’ll let you know how it works out :)

]]> By: Jim Moore [Visitor] http://blackbeanbag.net/wp/2006/10/04/tod-golding-on-tdd/comment-page-1/#comment-9 Thu, 05 Oct 2006 12:39:49 +0000 http://blackbeanbag.net/wp/?p=20#comment-9 Um, so does that mean we should start using TDD for our test cases? If you’re not supposed to refactor without test cases to back you up, how do you refactor your tests as they change?

Obviously I’m being fairly tongue-in-cheek, but the underlying question is very real: Because we can’t treat test code “just like” production code, what are the differences and how do we manage them?

]]>