Visual Studio Tests

Test engine type

Select the tool used to run tests: VSTest or MSTest.

Test engine version

Select the version of the tool from the drop-down. By default, the available VSTest and MSTest installations are autodetected by TeamCity:

• MSTest versions 2005-2017 are supported.

• VSTest versions 2012-2017 are supported.

You can specify a custom path to the test runner here as well. TeamCity parameters are supported.

Test file names

This field is mandatory for VSTest and optional for MSTest. Specify the new-line separated list of paths to assemblies to run tests on in the included assemblies list. Exclude assemblies from the test run by specifying paths to them in the corresponding field. Wildcards are supported. Paths to the assemblies must be relative to thebuild checkout directory.

Run configuration file

(Optional) Specify the t ypical.runsettings file for VSTest or .testsettings file for MSTtest. You can use the file browser .

Additional command line parameters

Enter additional command line parameters for the selected test engine. Note that tests run with MSTest are not reported on-the-fly. The Microsoft Developer Network lists the available options for VSTest and MSTest.

Target platform

Select the platform bitness. Note that specifying x64 target platform will force the vstest.console process to be run in the isolated mode

Framework

If the default is specified, vstest.console will select the target framework automatically. You can also choose the .Net platform manually using the drop-down.

Test names

(optional) O f all tests discovered in the included assemblies, only the tests with the names matching the provided values will be run. For multiple values, use new line.

If the field is empty, all tests will be run. See details in the Microsoft documentation. Cannot be used with the option below.

Test case filter

Run tests that match the given expression. See details in the Microsoft documentation. Cannot be used with the option above.

Run in isolation

Run the tests in an isolated process

Use real-time test reporting

• If this checkbox is selected, a custom TeamCity test logger will be used for real-time reporting. See the next section for details.

• If not selected, VSTest will report tests to TeamCity after the run ( the discovery of custom logger will not be attempted).

MSTest metadata

Enter a value for /testmetadata:file argument. See details in the Microsoft documentation

Testlist from metadata to run

Edit the Testlist. Every line will be translated into /testlist:line argument. See details in the Microsoft documentation.

Test

Names of individual tests to run. This option will be translated into the series of /test: arguments. See details in the Microsoft documentation.

Unique

Run the test only if one unique match is found for any specified test in test section

Results file

Enter a value for the /resultsfile:file name command-line argument. Parameter references are supported. It is recommended to leave the field blank to generate a temporary *.trx file in the build temporary directory. Note that the directory may be cleaned between the builds.

To save the test run results to a named non-default file, enter a value for the /resultsfile:file name command-line argument.

• • If the path specified is relative, it will be relative to the build checkout directory. If the specified file already exists in the checkout directory, the build agent will attempt to delete the file. If the agent fails to delete it, the build will fail.

    To create a *.trx report in the build temporary directory, use %\system.teamcity.build.tempDir%.

  • If the path specified is absolute, it will be used "as is".