Jeremy Miller has a great post about Microsoft’s guidelines for Test Driven Development in VS 2005.

Anyone that’s done TDD for any length of time will agree with what Jeremy has to say.  My biggest complaint with Microsoft’s recommendations is the autogeneration of tests.  I commented on this here and I’ll say it again….where is the Red, Green, Refactor in autogenerating tests?  TDD is about writing the test, writing the code and then refactoring.

Jeremy says:
By the way, you can do TDD and Continuous Integration with free open source tools that might actually work better than the VSTS alternatives.  For doing rapid TDD, the consensus view seems to be that the combination of NUnit or MbUnit and TestDriven.Net is superior in productivity to the new VS 2005 unit testing capabilities.

Since I don’t have VSTS, I’ll continue using the free, open source tools.  If you haven’t checked them out yet, make sure you do:
NUnit
TestDriven.Net

For more information on TDD in .NET, check out this great list of links compiled by Darrell Norton.

Now playing: Duran Duran - Lonely In Your Nightmare