Comments on: Refining My TDD Strategy http://www.caffeinatedcoder.com/refining-my-tdd-strategy/ A Grande, Triple Shot, Non-Fat Core Dump by Russell Ball Wed, 01 Feb 2012 19:33:39 +0000 hourly 1 http://wordpress.org/?v=3.1.3 By: The Value of Testing « The Occasional Blogger http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-6778 The Value of Testing « The Occasional Blogger Wed, 28 Sep 2011 23:37:44 +0000 http://www.caffeinatedcoder.com/?p=836#comment-6778 [...] just wanted a highlight a post over at the Caffeinated Coder because I thought it was particularly well thought out. In it Russell talks about his changing [...] [...] just wanted a highlight a post over at the Caffeinated Coder because I thought it was particularly well thought out. In it Russell talks about his changing [...]

]]> By: Russell Ball http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-2584 Russell Ball Thu, 18 Mar 2010 08:37:47 +0000 http://www.caffeinatedcoder.com/?p=836#comment-2584 @Franz - Thanks for the resource suggestions. I already own Working Effectively with Legacy code and have it on my reading list for the near future (my May book). I'll put the other 2 resources on my list of things to check out. Thanks! @Franz – Thanks for the resource suggestions. I already own Working Effectively with Legacy code and have it on my reading list for the near future (my May book). I’ll put the other 2 resources on my list of things to check out. Thanks!

]]> By: Franz See http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-2583 Franz See Thu, 18 Mar 2010 06:36:25 +0000 http://www.caffeinatedcoder.com/?p=836#comment-2583 Sadly, the usual response when TDD gets in the way is to fix the Tests or the Testing process instead of paying attention to the smells which would lead to refactoring the production code. However, it is hard to find ways in fixing these smells not unless you are aware of the patterns. Personally, I would suggest the books xUnit Test Patterns and Working Effectively with Legacy Code. And most importantly, the TDD mailing list ! :-) It's easier/faster to learn from other people's experiences than from your own mistakes :-) Sadly, the usual response when TDD gets in the way is to fix the Tests or the Testing process instead of paying attention to the smells which would lead to refactoring the production code.

However, it is hard to find ways in fixing these smells not unless you are aware of the patterns.

Personally, I would suggest the books xUnit Test Patterns and Working Effectively with Legacy Code. And most importantly, the TDD mailing list ! :-)

It’s easier/faster to learn from other people’s experiences than from your own mistakes :-)

]]> By: Jon Limjap http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-2582 Jon Limjap Thu, 18 Mar 2010 05:08:30 +0000 http://www.caffeinatedcoder.com/?p=836#comment-2582 I personally already follow these guidelines in one way or another. It's literally difficult to enforce TDD within a team that's not interested in it anyway, so this is a nice compromise -- sometimes the only compromise -- that will work. I personally already follow these guidelines in one way or another. It’s literally difficult to enforce TDD within a team that’s not interested in it anyway, so this is a nice compromise — sometimes the only compromise — that will work.

]]> By: Ruben Steins http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-2571 Ruben Steins Thu, 11 Mar 2010 09:47:24 +0000 http://www.caffeinatedcoder.com/?p=836#comment-2571 A certain degree of healthy pragmatism will save you a great deal of work here. So, I don't think you're way off base at all. Actually I think the distinction between throw-away-tests and commited tests (that actually protect complex or important code) seems very natural to me and make perfect sense. A certain degree of healthy pragmatism will save you a great deal of work here. So, I don’t think you’re way off base at all.
Actually I think the distinction between throw-away-tests and commited tests (that actually protect complex or important code) seems very natural to me and make perfect sense.

]]> By: Giorgio Sironi http://www.caffeinatedcoder.com/refining-my-tdd-strategy/comment-page-1/#comment-2562 Giorgio Sironi Fri, 05 Mar 2010 11:37:51 +0000 http://www.caffeinatedcoder.com/?p=836#comment-2562 "I often seem to write code that must fit into an existing design, follows a well known pattern" This way there is no driven design anymore: patterns usually *emerge* from a design, you shouldn't force them from the start. Good design and ease of testing go hand in hand. I'm all for having less code to maintan, maybe you should take a look at refactoring *also* test code because it has the same importance as production code. For example: http://xunitpatterns.com/ “I often seem to write code that must fit into an existing design, follows a well known pattern”
This way there is no driven design anymore: patterns usually *emerge* from a design, you shouldn’t force them from the start.
Good design and ease of testing go hand in hand.
I’m all for having less code to maintan, maybe you should take a look at refactoring *also* test code because it has the same importance as production code. For example:
http://xunitpatterns.com/

]]>