tdd

I think I'm only on step 4. Interesting to think about.

Jaybe introduced me to the Visual Studio Unit testing and "Test Driven Development" methodology. I can't say I agree with every aspect of TDD when carried to the extreme but there are some parts I like a lot:

- Write (failing) unit tests BEFORE writing your code. (But I think you do need to do some design work and object modeling before you can start the unit testing).
- Use code coverage to make sure you're getting very high % coverage of all your code before considering your tests complete.

Part I'm not so keen on is writing code that is a "stub" for the actual working system. It seems to me this leads to a lot of writing and re-writing of code that is going to get thrown away. If you're going to write the "minimum implementation" for getting your unit tests to pass, I still think this needs to be mostly NOT throw-away code. Otherwise, how is this making "progress"?

Quoted: The purpose of this project is to build some insightful and practical guidance around using Visual Studio Team System 2005. It's a collaborative effort between patterns & practices, VSTS team members, and industry experts.

Transactional test fixtures

test drive development in .net

Quoted: In this article Doug Seven will introduce you to Test Driven Development and show you how to incorporate this design methodology into you daily coding habits using Visual Studio 2005 Team System.