.NET unit testing packages [closed]

Answer 1

I like TestDriven.NET (even though I use ReSharper) and I'm pretty happy with XUnit.net. It uses Facts instead of Tests which many people dislike but I like the difference in terminology. It's useful to think of a collection of automatically provable Facts about your software and see which ones you violate when you make a change.

Be aware that Visual Studio 2008 Professional (and above) now comes with integrated Unit Testing (it used to be available only with the Team System Editions) and may be suitable for your needs.

Answer 2

xUnit.net looks like it provides a slightly different approach to NUnit, MbUnit, and MSTest, which is interesting.

In my search for an RSpec-like solution (because I love the RSpec), I also came across NSpec, which looks a bit wordy, but combined with the NSpec Extensions addon to use C# 3 extension methods, it looks pretty nice.

Answer 3

I like MbUnit, er, Gallio. Most importantly to me is having good tools support inside Visual Studio. For that I use Resharper, which has an MbUnit test runner. A lot of folks seem to like TestDriven.NET as their test runner as well.

Answer 4

I use the following:

TestDriven.NET - Unit testing add on for Visual Studio

Typemock Isolator- Mocking framework for .NET unit testing

NUnit - An open source unit testing framework that is in C#.

Answer 5

NUnit, MSTest, etc. all do pretty much the same thing. However, I find NMock indispensable.

NMock or any mocking package is not unit testing, but it makes it so much easier to do unit testing that it might as well be.

Answer 6

We use NUnit and MbUnit here. We use TestDriven.NET to run the unit tests from within Visual Studio. We use the excellent, highly recommended RhinoMocks as a mock framework.