Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Research Testing Tools for .NET Developers

Testing Tools for .NET Developers


InfoQ's research widget has been deprecated and is no longer available.

It often happens that the tools we rely on the most are also the most immature. We tolerate them because they fulfill an essential role. Other tools are really well designed, but aren’t important enough to justify the cost in time and money. And a rare few hit both marks. InfoQ wants to know which tools .NET testing tools you like to use and which you need to use.

InfoQ wants to know which .NET testing tools are first rate, which are immature and unreliable, and which are so important that you use them despite their failings.

Here are the options:



Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • You're missing some tools!

    by Matt Honeycutt,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I'm biased, but I'd like to see SpecsFor and SpecsFor<Mvc> on this list. Granted, I created both, but I know many teams are using them.

  • for unit testing

    by Johannes Erb,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    My focus is more on the programming side than on actual testing - i.e. I am not an expert on testing. For unit tests, however, when working with .Net, I personally prefer over NUnit. Also missing in your list...

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p