How do Visual Studio’s testing tools compare to third-party frameworks like NUnit? Are there any significant differences?
How do Visual Studio’s testing tools compare to third-party frameworks like NUnit? Are there
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How do Visual Studio’s testing tools compare to third-party frameworks like NUnit? Are there any significant differences?
For me MsTest (comparing to MBUnit, NUnit and XUnit.net) is sufficient in terms of features.
The integrated runner is Ok, it works faster than Resharper’s runner and produces better output (IMHO), however, left-clicking on unit test item in the runner gets you to the output instead of the unit-test source, which is very non-intuitive and annoying.
My biggest problem with MsTest currently is that it drops all binaries and other deployment items for the test session into a single folder. This is really bad if you have multiple test projects in your solutions with, say a different Spring.Config in each project.
–UPDATE–
A year after I wrote this answer, I’m convinced MsTest is NOT the way to go, not for new projects. The biggest problem with it is lack of support for inheritance for the Test classes’ TestInitialize methods. Plus, MsTest requires you to have Visual Studio installed on the build server!