VS 2013 MSTest vs nUnit vs xUnit
<p>I realize there have been a LOT of questions on this topic but somehow I haven't found one that addressed my needs.</p>

<p>My team is looking to start automated Unit testing our application. We have never done it before and nobody on the team has much experience with it. I have been asked to research and find a framework for automating our Unit Testing. So far, I have narrowed the choices down to <strong>MSTest, NUnit and xUnit</strong>. </p>

<p>All across the internet, I read negative reviews about MSTest but it seems the most convenient tool to me for our purpose.</p>

<p>1) Our application is .NET</p>

<p>2) We use licensed VS IDE for our development across the team.</p>

<p>3) Source Control is Team Foundation Server 2010 </p>

<p>4) We plan to integrate CI/CD as part of our software delivery process.</p>

<p>I feel that <strong>MSTest</strong> integrates right into this setup and provides the cleanest interface for us to work on. Is there a significant advantage with <strong>NUnit</strong> or <strong>xUnit</strong> over <strong>MSTest</strong> that we should consider? </p>