November 2005 - Scott Bellware [MVP]

Author: Scott Bellware
Following Test-Driven Development, a developer first writes a failing test, then makes the test pass, and then writes the functional code that the assertions of the test are meant to lock in. This is an overly simplistic view of TDD, but it's a level of understanding that many folks never really see beyond. If you stop at such a shallow understanding of TDD, you'll probably end up scratching your head and wond

Microsoft practice guidance for Test-Driven Development is pure marketing propaganda. Here's some guidance on that guidance with hopes that you don't get suckered by this shameless attempt by Microsoft to kill one of the most important advancements in software development practice.