Documentation for Bamboo 4.1.x. Documentation for earlier versions of Bamboo is available too.

This page describes how to configure a MSTest Runner executable for a Bamboo task. The MSTest Runner executable runs and parses tests for .NET builds.

When creating a new job or configuring an existing one, you need to specify the tasks that will execute the job's builds. You must specify an executable for each task. If you specify an Ant, Grails or Maven executable, you will also need to choose a JDK.

When creating a new plan, you can configure the tasks for the plan's default job.

An executable is a program external to Bamboo used to automate processes. Generally, executables compile source code to generate compiled executable files (referred to as artifacts in Bamboo). Ant, Maven, MSBuild or PHPUnit are just some examples of executables that can be used as part of your build process.

New executables can be defined as capabilities in Bamboo. Once an executable has been defined in Bamboo, it can be configured as part of a task.

Configuring a MSTest Runner executable for a task

Before you begin:

  • .NET builder tasks in Bamboo (e.g. NAnt) do not parse test information as part of the task. You must configure a test task (e.g. MSTest Parser), if you want test results from the builder task to be parsed.

To configure a MSTest Runner executable for a task:

  1. Navigate to the task configuration for the job (this will be the default Job if creating a new plan).
  2. Click the name of the desired MSTest Runner task, or click Add Task and then MSTest Runner if creating a new task.

  3. Update the task settings:

Related pages:

SettingDescription
Task DescriptionA description of the task, for display in Bamboo.
Executable

The MSTest Runner executable that you wish to use for this task (e.g. "Visual Studio 2010"). The executable that you select will become one of the task's capability requirements (and hence, one of the job's requirements). For details, please see Configuring a job's requirements.

Specifically for MSTest, we recommend the executable to be defined with the Visual Studio IDE folder path. Example:

C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\

This will allow Bamboo to find the necessary resources.

Environment VariablesAny extra environment variables you want to pass to your build. e.g. JAVA_OPTS="-Xmx256m -Xms128m".
ContainerThe test container, i.e. the file that contains the tests you want to run. For example, tests.dll. The value of this field is passed to the MSTest.exe as the /testcontainer parameter. See MSTest.exe Command-Line Options (MSDN).
Test MetadataThe path to the Test Metadata file relative to the working directory. For example, "MyApp\MyApp.vsmdi"
Result FilenameThe file that you want to save the test results to. For example, testResults.trx. The value of this field is passed to the MSTest.exe as the /resultsfile parameter. See MSTest.exe Command-Line Options (MSDN).
Run ConfigurationThe run configuration that you want to use. For example, localtestrun.Testrunconfig. The value of this field is passed to the MSTest.exe as the /runconfig parameter. See MSTest.exe Command-Line Options (MSDN).

  • No labels

1 Comment

  1. Sean Dockery

    Aug 06, 2012

    I've been experimenting with the MSTest Runner and used the simple values depicted in the screenshot on the right-hand side of this page.  That is, I am using Visual Studio 2010 and have specified a Result Filename with a value of testresults.trx.  On subsequent builds of my project, the build fails with the error:

    The results file "testresults.trx" already exists. Please specify a different results file or verify the existing file is no longer needed and delete it.

    In order to work around this problem, I've changed the Result Filename to a value of testresults-${bamboo.buildNumber}.trx.  This avoids the name collision but results in trx files needlessly accumulating in the project working directory.

    Is there a simple alternative or recommended way (other than a "force clean build") in which I should be configuring the MSTest Runner task that will avoid having these trx files pile up?




Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.