Favorite .NET Unit Testing framework [closed]

Answer 1

I have used both NUnit as well as MS Test. I like the integration of MS Test with the IDE and additional benefit of code coverage as well. But due to the performance reason as well as things like fluent assertions I prefer to use NUnit over MS test.

You can write framework agnostic asserts using a library called Should. It also has a very nice fluent syntax which can be used if you like fluent interfaces. I had a blog post related to the same.

http://nileshgule.blogspot.com/2010/11/use-should-assertion-library-to-write.html

If we use something like Should for assertions then both versions of test almost lokks the same and I don't see much difference between the two frameworks.

I had done a comparison of NUnit and MSTest unit testing frameworks in one of my blog.

Answer 2

xUnit.net, but I'm hardly unbiased. :)

Why I use it: http://www.codeplex.com/xunit/Wiki/View.aspx?title=WhyDidWeBuildXunit

Answer 3

I like xUnit because of the way it uses the constructor and Dispose methods instead of having to apply attributes to other methods for initialization and all that.

Answer 4

The support for NUnit tests in Resharper is great and sets the bar very high for me moving away from NUnit. I can run all the tests in a solution directly from Visual Studio, or I can drill down and concentrate on specific tests. When my code is checked in, my continuous integration build runs the same tests. This gives me a lot of confidence in my development process.

Answer 5

MSTest

http://en.wikipedia.org/wiki/MSTest

I don't know if it's my favorite (haven't really tried many others), but it's convenient since it's built into Visual Studio.

Answer 6

I've used nUnit for years, but when we moved to VS2008 and TFS 2008 (using TeamBuild) we decided to try MSTest. No huge complaints there... we really like how well it integrates with the IDE as well as the CI build server.

One new thing we're trying which looks to have awesome potential is another add-on from Microsoft Research called Pex (requires VS2008). As they put it: "Pex generates unit tests from hand-written parameterized unit tests through automated exploratory testing based on dynamic symbolic execution." The way I put it is: this thing does static analysis on your unit test and target code and codegen's unit tests to achieve super high code coverage (which is often impractical if you're doing it by hand).