Note that there are some explanatory texts on larger screens.

plurals
  1. POHow much faster is NUnit compared to MSTest
    primarykey
    data
    text
    <p>Roy Osherove, author of <em>The Art Of Unit Testing</em>, has <a href="http://weblogs.asp.net/rosherove/archive/2010/03/05/nunit-vs-mstest-nunit-wins-for-unit-testing.aspx" rel="nofollow noreferrer">commented</a> on a blog that of the many things NUnit supposedly does better, it being <strong>much</strong> faster is one of them. </p> <p><strong>My question is how much faster though, if at all? Are we talking an order of magnitude? 10%? 50%?</strong></p> <p>I'm asking this because for the moment I can't compare the two. I am trying to setup my test project to be in a <a href="https://stackoverflow.com/questions/92869/nunit-vs-visual-studio-2008s-test-projects-for-unit-testing">dual-mode</a> so that I can switch between them. Unfortunately, I am having a problem with NUnit integrating with the latest version of Microsoft Moles, and also <a href="https://stackoverflow.com/questions/3796140/log4net-issues-with-nunit-tried-v2-5-7-2-5-2-2-4-8-2-4-7">NUnit is conflicting with a third party library (appears log4net related)</a>.</p> <p>So far MSTest seems so much easier to use within Visual Studio 2008. All of the version issues and compatibility problems with NUnit (at least for me) is steering me towards choosing MSTest as the framework for the project (though I may keep the dual mode option). Another plus for MSTest is that I can still use most of NUnit asserts with:</p> <pre><code>using Assert = NUnit.Framework.Assert; using Is = NUnit.Framework.Is; </code></pre> <p>But.... If speed is truly much faster in NUnit, then I'd prefer to use it, despite the pain points. </p> <p><strong>Lastly, has there been any speed improvement in VS2010 for MSTest</strong>?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload