Oh, another thing that is worth mentioning is that I am going to talk about Test Driven Development and Interaction Based Testing at the VB.Net User Group meeting next week (Wendesday, 04 July, 2007).
More details can be found here: http://www.renaissance.co.il/ivbug/
The first one is:
Getting to know Test Driven Development & Design
You have just finished implementing the new WizBang 2.0 feature, and you are feeling pretty good about yourself. But, do you know if this feature broke? Testing using F5 isn't scaling beyond the simplest application, and the cost of maintaining software is often several times over the cost of building it.
The second one (I gave that one in DevTeach):
Beyond the simplest scenarios, all objects had collaborators that they work with. This flies in the face of testing objects in isolation. This is the problem that mock objects were created to solve. In this talk you will learn what mock objects are, how to utilize them and best practices on when / how to utilize them. Rhino Mocks is a mock objects framework for .Net whose core goals are to let the developer rely on the compiler work well with refactoring tools.
The last time I did any serious VBing was quite some time ago, so I encourage you to come and watch how I humilate myself in public ;-)