At work the other day I had some trouble using the TestDriven.Net 1.0 plugin for Visual Studio 2003. When I ran my tests using TestDriven, no test results where shown in the test output window. Instead I got stuck with a dozen or so test output windows, all of them empty... I tried re-installing the tool and repairing my Visual Studio installation but non of the things I tried really helped.
I was still able to debug my code using te "run with debugger" option but to see some test results I had to use NUnit, which is a separate tool outside the IDE. This was not too big of a deal but it was decreasing productivity and I wanted it fixed.
While I didn't expect too much of it I decided to send an email to the TestDriven.Net support. It didn't take long before I had an anwser from Jamie Cansdale, the creator of TestDriven, with some suggestions of what to try. Unfortunately his suggestions didn't help either but Jamie wouldn't give up. He really cared about the problem at hand and that alone was enough for me. We exchanged quite some emails that day but still without any result. Nonetheless I want everybody to know TestDriven.Net really knows how to give support. After all it's the experience that counts! A positive experience it was!
Unfortunately I was unable to test the newer version of TestDriven because we don't have any licenses for it. It would most likely have solved the problem... With Visual Studio 2005, unit testing is build into the IDE. Running tests and viewing test output is done in a nice way but I miss being able to right click a test method and just run it from there with the debugger. With TestDriven.Net 2.0 comes support for Visual Studio Test projects. When I'm able to fully swith to VS 2005 someday, I will still love to have TestDriven.Net just for running my test directly from the code window.