TestDriven.NET…


I came across a link to TestDriven.NET today. Given that I'm not as plugged into the C# space as I used to be, I hope this is news to at least some of you.


TestDriven.NET is a VS add-in that builds on top of NUnit to give you IDE integration for your unit testing features.


I haven't had a chance to try it - if you have, please post your opinion in the comments.

Comments (17)

  1. SuperJason says:

    I’ve been using it for about a year and it’s hella-cool. I don’t even have to open up NUnit any more. It speeds up development and unit testing dramatically. I highly recommend it.

  2. Matt Davis says:

    I’ve used it for several months now, and I don’t have much bad to say about it. It definitely makes debugging unit tests a lot easier, since you can just right-click a Test method in the IDE and run it in the debugger (it’ll automatically spin up a host process and attach for you), rather than manually attaching to a (*)Unit process.

    On the down-side, most of the output is textual- it will make additions to your TaskList for failed tasks, but it’s much less satisfying than "going all green" in NUnit. 🙁 Since that’s the worst thing I can say about it, I guess I’d have to give it two thumbs up!

  3. MattHope says:

    Extremely useful for debugging test failures as Matt Davies says.

    However I encounter a lot of instability with it if I do anything else. It crashed VS one too many times and I decided I would never use it for anything except the debugging (where it crashes surprisingly rarely and is sufficiently useful in this respect to more than outweigh the risk)

    That said it is well integrated an causes me no issues if it just sits there without being invoked so I whole heartedly recommend trying it to anyone.

    It does expose an annoying behaviour of VS though – installing the add in removes most UI alterations I had made (new tool bar buttons/arrangement) This is insanely annoying i you spend ages getting your IDE just right and lose all your (unsaveable) settings 🙁

    To be honest I look forward to VS 2005 doing it sufficiently well to not need this, but a very good tool none the less (and the latest build seems considerably better stability wise)

  4. stevef says:

    Great tool and remember all it is free so with that a little instability is a given but it is improving with every build and the last build is very stable.

    Integration with the ide is good

  5. TestDriven.NET is absolutely invaluable – I can’t imagine trying to develop in a test-first fashion without having this stuff baked into the IDE.

    For 2005 users, it is worth noting that it integrates nicely with Beta 2.

  6. For me it is a must. Very, very useful

  7. John Bullock says:

    Very cool tool. Much better than previous versions. Very easy to use.

  8. Chris Kinsman says:

    TestDriven.NET is awesome. Could not live without it in Everett today.

  9. Simon says:

    I’ve used it for a while now, and I find it more convenient that the NUnit GUI. I’ve assigned a shortcut key to run the tests, which makes it even more useful. I’d recommend it.

  10. Rex says:

    It’s actually based on the open-source NUnitAddin project run by the same chap, however now NUNitAddin has been discontinued, and TestDriven.NET is not open-source 🙁

    this means that the benefits of TestDriven.NET are useless to us, because we’ve written our own unit test framework (similar to NUnit, but written when NUnit was still a baby)….I dont think we can extend TD.NET for our framework without source….

  11. Jason Kemp says:

    I’ve been using it since it went 1.0. It’s a really great tool for checking new tests and ensuring that your editions to code fixed broken tests. I still whip out NUnit on occasion to get the green. That’s my only criticism: no green bar. And it supports more than just NUnit. It has support for MbUnit, and, I believe, Team System. It works in both VS2003 and VS2005 too.

    It’s a must have.

  12. Miki Watts says:

    I’ve been working with TestDriven.Net for some time now.

    It works just great, I linked the test solution event to a keyboard shortcut and that has become my new build shortcut key 🙂

  13. A+

    If you’re unit testing in VS.NET 2003 using mbUnit or NUnit, then it is a must-have.

  14. seer says:

    I use it almost from it start days, when it was called NUnit addin.

    It’s usefull not only for unit testing, but in my case also for manual tests how my control works – I don’t need to add special project with exe to see my UserControl which later will be used only in IE.

    But some instabilities also must be noted.

  15. Jeff Key says:

    I only use two VS add-ins: this and ReSharper. The concept and execution are great. Invaluable if you’re doing TDD.

  16. I have been using it since it’s open source days as NUnitAddin. I must say, from viewing the previous comments to this blog, I appear to be the exception, but I have not experienced any instabilities at all… And I use it A LOT!!!!

    In fact, NUnitAddin was available when I first got turned on to NUnit, so I have actually never used the NUnit GUI.

    I strongly recommend it.I have been using it since its open source days as NUnitAddin. I must say, from viewing the previous comments to this blog, I appear to be the exception, but I have not experienced any instability at all… And I use it A LOT!!!!

    In fact, NUnitAddin was available when I first got turned on to NUnit, so I have actually never used the NUnit GUI.

    I strongly recommend it.

  17. Ha! That’s what I get for trying to use word to spell check my previous comment… I pasted it twice :S

Skip to main content