Test-Driven Development in Microsoft .NET, by James W. Newkirk and Alexei A. Vorontsov, seems primarily intended for programmers that are convinced that TDD is a “good thing” and are writing “enterprise” applications with ASP.NET and ADO.NET in which even one minor defect is one too many. Since only one of those things apply to me (I am a programmer), it should come as no surprise that I did not get much out of this book, and ended up skimming most of it. If you fit the profile better than I do, you will probably like this book a lot more than I did.

I did enjoy the first three chapters, as well as Appendix A, as they teach the basics of TDD by example. TDD seems most logical when developing small, independent components without user interface. Even that looks like an awful lot of work, and it seems to me that the work could increase exponentially with larger, codependent, and/or user interface driven components. Perhaps experience can mitigate some of that, but I don’t think I’m ready to commit the extra time and energy.