TestDriven.Net
I’ve been using NUnit for about 2 months now, and I love
it. It’s great to be able to make sweeping changes to the inner workings
of my class libraries, and then ensure that everything is still working, without
having to think about if I missed something. Just run the tests, if its
all green, you’re good to go!
I first heard about TestDriven.Net from Sam Gentile, he feels its a wonderful tool, and I know many other people do too.
So I tried it out, thinking that it would be nice to have integration into
visual studio with my unit tests. I gotta say though, after using it for a
little bit, I don’t like it very much. I’ve gotten used to being able to
glance and tell by the color on the screen what the status of my tests are, and
the output window in visual studio doesn’t give me the same fulfilling
experience. Also, the NUnit gui is fast and responsive, and I missed that
as well after using visual studio to run the tests, because its just another
thing to slow down the IDE, I really didn’t mind having to run a separate
application to run my tests, especially since they are database intensive and
take over 100s to run them all.
One thing that I couldn’t use was the Test With Debugger
feature because I am using Visual C# Express 2005, and I can’t seem to
debug. But what I usually do when I use NUnit, is just attach the IDE to
nunit-gui.exe in order to debug my tests. I was comfortable with this, but
I think that feature of TestDriven.Net might make me keep it
installed.
Does anybody feel the same way? Or am I a moron who’s out on
a limb 
Anonymous said,
Wrote on December 10, 2004 @ 12:12 am
I have felt the same way. At this point I believe that this is just a lack of knowledge on my part. I have found how to launch various xUnit GUI’s from within TD.NET but I sure would like red/green when I selected to run a test. Its hard to find the one or two failures in an output window.
Anonymous said,
Wrote on December 10, 2004 @ 1:57 am
As well as sending to the output window, it also populates the Task List. You can double click on a Task List Item and it will take you to the offending code. You can also double click on stack traces in the output window and be taken to the corresponding code.
I hope that helps.