Many people have commented on the release of TestDriven.NET, including Sam and Scott.

I tend to agree that it is a cool tool, and the integration with the IDE is very impressive. One thing I'd like to see, though, is a more visual form of feedback. While output to the output window is nice, it means I have to go and read what it means to see the outcome of the test. while I'm not a big fan of NUnitGUI, I must admit that the red/green semaphores are an attractive and easy way to visualize the results of the tests. (If there is something better than the output window in TestDriven.NET, someone please tell me.... but please don't say the Task window!). Another thing I did notice is that it is a little on the slow side, but since one would use it to run a single test method at a time, I figure that's ok.

Unfortunately for me, it doesn't work very well (or at all) on our current working development system. The problem is that TestDriven.NET seems to rely a lot on the VS.NET project system, which we barely use. We all build around here with NAnt, and basically have a single VS.NET project containing the entire source tree (it's not that big, and we have it split over several of those). This gives us intellisense and designer support, which pretty much seem to be the only reason for using VS.NET as the IDE at this stage. Any tips here would be welcomed :)

Tomas Restrepo

Software developer located in Colombia.