title: Visual Studio 2012 MSTest vs NUnit pros and cons
body: <p>We have to decide which technology to use for our unit testing. Currently we use Visual Studio 2010 and not happy with MSTest that came with that. It is buggy, poor in deployment (E.g the test setting output directory is not recognized correctly), and have several issues when trying to test assemblies in 32bit and 64bit versions. To make matters worst MSTest does not have a good impedance match with our Jenkins build system. We therefore thought of moving into NUnit. However, no one in our team has a good exposure to NUnit. Also,we will be soon moving into Visual Studio 2012. </p>
  
  <p><strong>I need to know the pros and cons of Visual Studio 2012 MSTest vs Nunit latest version</strong>. Since most of the articles on stack overflow are related to older versions of VS they are not related to us. I guess Microsoft has  improved MSTest a lot since 2010. Please provide an unbiased comparison with detail technical issues you have faced in both technologies (<strong>newer versions only</strong>) </p>