Unit test, NUnit or Visual studio?
c#, nunit, unit-testing, visual-studio
Solution
NUnit has few advantages over MS-Test
- Suite attribute - can aggregate tests and execute them separately (useful for large projects with fast and slow tests for example)
- Readable Assert method, e.g. `Assert.AreEqual(expected, actual)` vs `Assert.That(actual, Is.EqualTo(expected))`
- NUnit has frequent version updates - MS-Test has only one per VS version.
- Many integrated runners including Resharper and TestDriven.NET
- Expected exception message assertion - can be done using attribute in NUnit but must be done using Try-Catch in MS-Test
- `[TestCase]`! NUnit allows for parameter-ized tests.
Problem
I'm using Visual studio (sometimes resharper) to run my unit test. I heard about NUnit, but I don't know many things about it... Should I care about it ? Can it offer something better than visual studio? Should I Use NUnit and why?