Is mspec better with or without nunit?

I have seen mspec used with nunit in some blogs and discussions. In fact, most of the examples on the Internet I've seen demonstrate mspec with some dependency or nunit integration. My team is trying to use mspec without nunit in a new ASP.NET MVC2 project. We are not yet at the stage of writing the specification, so I can not say which is better. What is your experience? Are there any advantages to using mspec with nunit? Without?

+3
source share
2 answers

MSpec is in no way dependent on NUnit or xUnit. Thus, you can use MSpec yourself, as it has its own runners and approval methods. The blog posts you saw most likely used the "old" assertion library, depending neither on NUnit nor on xUnit. This dependency was removed at the end of 2009.

What you can do, although this is not required and I see no benefit in this, is to use the NUnit ( Assert.IsTrueand others) assertion library along with MSpec.

+10
source

since you haven't started yet, look at SpecFlow, it blends perfectly with MSTest and Visual Studio ....

-3
source

Source: https://habr.com/ru/post/1740024/


All Articles