ms style tdd - tool-driven development?
stumbled on microsoft's guidelines for test-driven development today, courtesy of testdriven.com and scott bellware. now, i'm no expert tdd'er - i'm a novice practitioner, and in sore need of much more practice - but even i'm disgusted by the way these "guidelines" completely ignore the fundamental precepts of tdd. generating tests from pre-existing interfaces? in tdd, it's the tests that drive the creation of the interfaces. funny thing is, elsewhere on the msdn site, there are more accurate guidelines for tdd, written back in 2003.
let the tests drive your code. red, green, refactor.
( more tdd info )
[edit] lol...in the time it took me to write this, the article in question has been removed from the msdn site. it had a rating of 1.16 out of 9 on 402 votes at the time of this edit. amazing how much power the blogosphere has. god bless the google cache.
let the tests drive your code. red, green, refactor.
( more tdd info )
[edit] lol...in the time it took me to write this, the article in question has been removed from the msdn site. it had a rating of 1.16 out of 9 on 402 votes at the time of this edit. amazing how much power the blogosphere has. god bless the google cache.