tdd

vbUnit3 helps to write and run automated unit tests against Visual Basic and COM objects.

NUnit Converterは，JUnit Converterを.NET用に移植したものです．

ひと言でいえば、プログラマーが単体テスト用のテスト・プログラムを作成し、それを実行することを支援してくれるものである。

ボトルネックを見つけるのに便利なプロファイラを作ってみた。

NDocでMSDN形式のドキュメントを作ると、ほとんど.NET Frameworkドキュメントと同じようなものが作れる

開発者向けツールだけでなく、プロジェクト管理ツールも紹介

CppUnit is a C++ unit testing framework.

Graphviz is open source graph visualization software. It has several main graph layout programs.

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.