BT
x Your opinion matters! Please fill in the InfoQ Survey about your reading habits!

Testing Tools for .NET Developers

by Jonathan Allen on Sep 16, 2013 |

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.

Tell us what you think

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

Email me replies to any of my messages in this thread

You're missing some tools! by Matt Honeycutt

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.

xUnit.net for unit testing by Johannes Erb

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 xUnit.net over NUnit. Also missing in your list...

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

Email me replies to any of my messages in this thread

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

Email me replies to any of my messages in this thread

2 Discuss
General Feedback
Bugs
Advertising
Editorial
InfoQ.com and all content copyright © 2006-2014 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT