Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The /publish option of MSTest.exe does a license check to ensure that a "Team" version of Visual Studio is installed (i.e. the Developer or Test edition) before it does the publish part of the code. </p> <p>This restriction appears to have been introduced to allow the basic unit testing capabilities in standard versions of Visual Studio but requires you to have one of the more expensive Team editions of Visual Studio to enable the "Team" related features in testing - such as to publish your test results to TFS.</p> <p>In total there are 3 missing features if you do not have a Team edition of Visual Studio with Team Epxlorer installed. </p> <ul> <li>Publishing to TFS</li> <li>Code coverage</li> <li>Connect to remote agent.</li> </ul> <p>If you have the Development Edition installed then you get publish and codecoverage but not the remote agent agent capabilities (i.e. for doing Load lesting).</p> <p>The Test Edition and Visual Studio Team Suite have everything.</p> <p>If you would like to see an example of a custom MSBuild task that uses MSTest.exe to publish unit test data from a build server (in this example JUnit test data), then take a look at the <a href="http://www.teamprise.com/products/build/" rel="nofollow noreferrer">Teamprise Build Extensions</a> that I wrote. The source code for these is available under the permissive <a href="http://www.microsoft.com/resources/sharedsource/licensingbasics/publiclicense.mspx" rel="nofollow noreferrer">MS-PL</a> open source license.</p>
 

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