Sara Ford starts a "what's wrong with this test case code" series. She begins with Identifying false positives. She also shows why it's better to LogPass than to LogFailure.

Scott Dockendorf blogs a follow-up to the Q&A session after his talk on Test Driven Development & .NET at the Plano .NET User Group, and also posts the slides and source code he used during the talk.

Len Holgate explains Why you're missing the point if you use a framework to generate Mock Objects for you: "TDD is all about the design. By writing a test before you write production code you think about the interface that clients of the production code will need to use. You're working as a client programmer and the tests will drive the design towards something that's nice to use from a client perspective. This is a Good Thing. In fact it's The Point!"

James Robertson attends the second meeting of the reorganized Maryland Agile/XP group and shares his impressions on the FitNesse demo.

JB Evain explains Type 6 IoC with a MockSystem example.

While adding unit testing to an existing system, Brian Oxley runs into a problem and solves it with delegation: "We're following the ancient dictum, any problem can be solved by introducing an extra level of indirection. Foo was already delegating doSomething() to Trouble; we just replaced that relationship with an extra level of delegation, Foo to NoTrouble to Trouble. Now I can mock or stub NoTrouble without needing access to Trouble."

Mike Hodnick finds Agile development for real and is thrilled: "I'm surprised that Agile Development hasn't caught on more quickly in organizations. After finally being able to work on a project while practicing Agile Development, it feels so natural."

The Wikipedia has an entry on TDD.