Comments on: TDD: Making the test green quickly

By: Mark Needham

Mark Needham — Wed, 27 May 2009 19:57:10 +0000

@J.P. Hamilton – agreed that's what we try to do as well. The weird thing is that when taking the small steps it sometimes feels that you're actually takings steps which are too small and are therefore slowing yourself down but nearly every time it turns out that the steps were too big!

By: J.P. Hamilton

J.P. Hamilton — Wed, 27 May 2009 12:12:11 +0000

This is what we do in all of our coding dojo's. After one our sessions, someone came up to me and said "TDD makes so much more sense now". It's really just taking "doing the simplest thing that works" to the extreme – baby steps. Your future tests will force you implement real code.

I like the flow that I get into when I code like this. I can make forward progress, doing TDD the whole way, without really knowing too much up front. Eventually, something will emerge, and I can refactor whenever I want.

By: DotNetShoutout

DotNetShoutout — Mon, 25 May 2009 04:29:30 +0000

TDD: Making the test green quickly – Mark Needham…

Thank you for submitting this cool story – Trackback from DotNetShoutout…

By: Nick Carroll

Nick Carroll — Sun, 24 May 2009 22:47:08 +0000

You did a much better job than me of explaining why it is a good thing to make a test pass quickly and how. My posts were meant to describe a tool — such as a chess clock — that could be used to help keep this in the minds of developers during a pair programming session, particularly when a developer continues to consecutively write a test and implement it for extensive periods.

By: Nick Carroll » Blog Archive » The Navigator role must have been coined by a keyboard hogger

Sun, 24 May 2009 22:41:30 +0000

[...] Mark does a better job of explaining how to make a test pass quickly and why it is a good thing. My idea of using a chess clock was aimed to keep this in the minds of developers during a pair [...]