5

I've been using NUnit for a few years. I've tried MBUnit for a short while as well as Zenebug and XUnit but I keep coming back to NUnit.

What is your favorite/most used Unit test Framework? Can you explain why you're using it?

Bill the Lizard
  • 398,270
  • 210
  • 566
  • 880
Dror Helper
  • 30,292
  • 15
  • 80
  • 129
  • 1
    have a look at this (german) poll: [link](http://windowsdeveloper.de/polls/Welches-NET-Unit-Testing-Framework-verwenden-Sie-172659) – Jan Köhler Apr 13 '14 at 09:27

15 Answers15

20

Nunit for the win!! It is simple and easy to implement. No mess, no fuss.

Craig
  • 11,614
  • 13
  • 44
  • 62
10

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

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

Brad Wilson
  • 67,914
  • 9
  • 74
  • 83
7

MbUnit

I like the way it handles reports, and I'm looking forward to some of the upcoming features I've heard about, such as integration with JsUnit.

Sam Wessel
  • 8,830
  • 8
  • 40
  • 44
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).

Kevin Dostalek
  • 736
  • 1
  • 5
  • 8
4

Gallio looks like it's going to be awesome once it gets more stable (currently alpha).

It's not just a test framework, but a test automation platform, so it will work with many existing test frameworks (MbUnit, NUnit, xUnit.net) yet be fully extensible, with a number of built-in additional features such as report generation in many formats and code analysis tools.

I've also heard that it will be able to

  • output image streams, so for example WatiN test failures can be output as screenshots, so you can see what state the browser was in when the test failed.
  • filter by namespace, so you can easily uncheck tests for an entire namespace before running them

Edit: It is indeed out of alpha now. We've tried it at our company and we really hated it. It was horrible to use and very slow. What a shame.

Sam Wessel
  • 8,830
  • 8
  • 40
  • 44
3

I've used Nunit for quite some time, but I happen to prefer things baked into VS. So, I'm now using MSUnit. Just a preference for having less add-ins installed in VS.

Jason N. Gaylord
  • 7,910
  • 15
  • 56
  • 95
3

NUnit. We can use it on CC.

Mariano
  • 2,928
  • 6
  • 25
  • 28
2

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.

Chris Pietschmann
  • 29,502
  • 35
  • 121
  • 166
2

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.

Max Schmeling
  • 12,363
  • 14
  • 66
  • 109
2

MbUnit has compatible syntax with NUnit but has more features (especially data driven tests).

craigb
  • 16,827
  • 7
  • 51
  • 62
2

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.

Lee
  • 1,576
  • 2
  • 15
  • 21
1
  1. xUnit - less ceremony, support for data driven testing and other extentions
Scott Weinstein
  • 18,890
  • 14
  • 78
  • 115
1

I used to use NUnit, but now I prefer the framework that comes with Visual Studio 2008, simply because it has tighter integration and is easier to set up to test private methods.

We also had problems with keeping the versions of NUnit synchronized with the rest of the team. It was a minor annoyance (go and upgrade, or fix the project references), but it went away with the switch.

Chris Wenham
  • 23,679
  • 13
  • 59
  • 69
  • 3
    I would try to not directly test private methods. The internals aren't usually what you're concerned about when testing. I take the black box approach: some input gives me some output that is supposed to be correct. – casademora Oct 05 '08 at 18:04
1

I've been using NUnit for some 4 years now, would definitely recommend using it. Reshaper - a plugin for VisualStudio by JetBrains includes a UnitTestRunner which integrates nicely with VisualStudio and lets you run / debug your tests from directly from the IDE. Resharper, NUnit and RhinoMocks is my preferred suite of tools for UnitTesting.

vikram nayak
  • 591
  • 5
  • 14
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.

Nilesh Gule
  • 1,511
  • 12
  • 13