Microsoft's horrible TDD guidelines
There has been much wailing and gnashing of teeth on various mailing lists over the MS article: Guidelines for Test-Driven Development that was recently posted.
Microsoft gets a lot of things wrong:
- write a "complete list of tests for a particular feature area" first
- then write the production code before the tests
- use the wizards to create the tests
- in typical VS style, the tool and the wizards dictate everything
- no mention of refactoring
- no mention on doing things in very small steps
- where are the feedback loops?
What a mess. There has been quite a response amongst the TDD community:
- Michael Feathers has a good post on this.
- Ron Jeffries' response - James Shore - Sam Gentile, with plenty of other links to other responses