Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 4.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Table of Contents

This page contains reference information for the sln2008 Build Runner that builds Microsoft Visual Studio 2008 solution files.

Icon

Note that sln2008 works the same as sln2005 only it uses MSBuild from .NET version 3.5

General settings

Option

Description

Build runner

Select sln2008 from the drop-down list.

Solution file path

Specify the path to the solution to be built relative to the build checkout directory. For example:

Working directory

Specify the build working directory. (optional)

Targets

Specify the Microsoft Visual Studio 2008-specific targets. The possible options are Build, Rebuild, Clean, Publish or a combination of these targets based on your needs. Multiple targets are space-separated.

Configuration

Specify the name of MS VS 2008 solution configuration to build.

Platform

Specify the platform for the solution. You can leave this field blank, and TeamCity obtains this information from the solution settings.

NUnit test runner settings

NUnit tests settings

Use this section to specify NUnit parameters

Tests platform

From the drop-down list select the desired execution mode on a x64 machine. Supported values are: Auto (MSIL) (default), x86 and x64.

NUnit runner

From the drop-down list select a version of the NUnit runner to use.

NUnit versions support

Icon

TeamCity NUnit Test Launcher supports NUnit versions 2.2.10, 2.4.1, 2.4.6, 2.4.7, 2.4.8, and 2.5.0.
TeamCity Addin for NUnit supports only 2.4.6, 2.4.7, 2.4.8, and 2.5.0.
TeamCity 4.5.6+ supports NUnit 2.5.2, and 2.5.3.

Run tests from

Specify the .Net assemblies, where the NUnit tests to be run are stored. Multiple entries are comma-separated; usage of MSBuild wildcards is enabled.
In the following example, TeamCity will search for the tests assemblies in all project directories and run these tests.

Icon

All these wildcards are specified relative to path that contains the solution file.

Do not run tests from

Specify .Net assemblies that should excluded from the list of found assemblies to test. Multiple entries are comma-separated; usage of MSBuild wildcards is enabled.
In the following example, TeamCity will omit tests specified in this directory.

Icon

All these wildcards are specified relative to path that contains the solution file.

NUnit categories include

Specify NUnit categories of tests that should be run. Multiple entries are comma-separated.

NUnit categories exclude

Specify NUnit categories that should be excluded from the tests to be run. Multiple entries are comma-separated.

Reduce test failure feedback time

Use the following option to instruct TeamCity to run some tests before others.

Run recently failed tests first

If checked, in the first place TeamCity will run tests failed in previous finished or running builds as well as tests having high failure rate (a so called blinking tests)

MSTest test runner settings

MSTest Settings

 

Run MSTests

Check the box to enable running MSTest tests. If the option is not checked only NUnit test runner will be used.

Path to MSTest.exe

A path to MSTest.exe file. By default Build Agent will autodetect MSTest installation. One may use %system.MSTest.9.0% to refer to found MSTest path

MSTest assemblies

A list of assemblies to run MSTests on. Will be mapped to /testcontainer:file argument

MSTest metadata

Enter a value for /testmetadata:file argument

Testlist from metadata to run

Every line will be translated into /testlist:line argument.

Test

Names of the tests to run. This option will be translated to the series of /test: arguments
Check Add /unique commandline argument to add /unique argument to MSTest.exe

Results file

Enter a value for /resultsfile:file commandline argument.

Additional commandline parameters

Enter an additional commandline parameters for MSTest.exe




See Also: