On Apr 1, 2006, at 4:04 PM, Jeffrey Thalhammer wrote:
I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes application code.
That approach is probably worth an experiment for some project, but it's not the "normal" meaning of Test Driven Development. In "normal" TDD you spend a very small amount of time writing a test, and then another alms amount of time writing *just enough* application code to make the test pass. Each mini-iteration might take between 1 and 5 minutes.
Here's a pretty good Power Point slide show that demonstrates the process:
http://www.butunclebob.com/files/downloads/Bowling%20Game%20Kata.ppt ------------------------------------------------------- Matisse Enzer <[EMAIL PROTECTED]> http://www.matisse.net/ - http://www.eigenstate.net/
