TeamCity provides support for MSTest 2005-2015 testing framework via parsing of the MSTest results file (
.trx file). The appropriate Microsoft Visual Studio edition installed on the build agent is required.
Due to specifics of MSTest tool, TeamCity does not support on-the-fly test reporting for MSTest. All test results are imported after the tests run has finished.
There are two ways to report test results to TeamCity:
Add the Visual Studio Tests runner as one of your build steps.
The easiest way to set up MSTest tests reporting in TeamCity is to add the Visual Studio Tests build runner as one of the steps to your build configuration and specify there all required parameters.
If the tests are already run within your build script and MSTest generates
.trx reports, you can configure service messages to parse the reports.
Autodetection of MSTest
Prior to TeamCity 9.1 the MSTest location was reported as system properties:
%system.MSTest.14.0% that referred to MSTest
Since TeamCity 9.1 system parameters of the
%system.MSTest.xx.yy% format were changed to configuration parameters of the
If system properties are required for the build, the mstest-legacy-provider plugin can be used.
TeamCity auto-detects MSTest based on the registry values that describe the Visual Studio installation path. If Visual Studio is installed in a non-standard location, or the registry key is corrupted, or the TeamCity agent has no access to the VisualStudio directory, TeamCity may not be able to detect MSTest. In this case, the corresponding configuration parameter of the
%teamcity.dotnet.mstest.xx.yy% format must be added to the build manually. It should contain the full path including the
MSTest.exe executable, for example, the default path for MSTest 2013 is
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\MSTest.exe.
Concepts: Testing Frameworks
Administrator's Guide: NUnit Support