OK. Here's part 2 of the TDD in practice dealio. I decided a screencast would be appropriate. I'm just getting over a cold so my voice is shot, this is a silent movie.

In part 1 I typed in code that I want, to solve my problem. Most of the code did not exist. So in part 2, we need to create everything that's missing and make the test pass. Play the video to see how I did it(I used all CodeRush features to generate code - with a little manual intervention; but most of this can also be done with raw Visual Studio shortcuts).

Go here for part 2.

Ok, so I've been meaning to do a screencast on this, i've done one but it's lame.  I figured I'd do more a photo slash journal-ish type thing and describe my real world(yes this is for an actual project) usage of TDD.  So here goes, I just typed the following into my test, this is what I want to do:

And that's pretty much it.  Notice the red squiggly lines? Yep, I haven't created that stuff yet, cuz this is what I want to do, not what I've done.  Next part will be making those red lines go away...

That's one of the funniest terms I've heard in awhile.  I heard it during the brilliant presentation by Giles Bowkett recorded at RubyFringe.