Microsoft Reverses on Misleading TDD Documentation

There’s been quite a stir over some documentation on MSDN about how to do TDD with Visual Studio 2005. Essentially it advocated writing all your tests first for a a particular class and then starting to implement the tests and get them to pass one by one. Sort of Big Design Up Front with Tests. Gee, might as well do a lot of UML diagrams and get the same effect. Basically what they were advocating was a TDD anti-pattern.

Anyway the community spoke up pretty quickly and loudly including Michael Feathers, Ron Jeffries, James Shore, and others. So it’s gone now and this is the Microsoft explanation.

Fairly impressive that this got changed so quickly.