Documentation for Bamboo 4.2.x. Documentation for other versions of Bamboo is available too.

This page describes how to configure a NUnit Runner executable for a Bamboo task.

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 NUnit Runner executable for a task

Before you begin:

  • .NET builder tasks in Bamboo (e.g. NUnit Runner) 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.

Related pages:

To configure a NUnit 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 NUnit Runner task, or click Add Task and then NUnit Runner if creating a new task.

  3. Update the task settings:

    SettingDescription
    Task DescriptionA description of the task, which gets displayed in Bamboo.
    ExecutableThe NUnit Runner executable that is available to perform the task. The executable that you select will become one of the task's (and so, the job's) requirements.
    You can add other executables, if required.
    NUnit Test FilesThe name of an assembly (.dll), Visual Studio project (.csproj), or NUnit Test Suite (.nunit) to test. See http://www.nunit.org/.
    Result FilenameThe name to be used for the XML results file.
    Tests to RunThe name of the test case, test fixture or namespace to run.
    Test Categories to IncludeSpecify one or more test categories, separated by commas, to be included in the test run.
    Test Categories to ExcludeSpecify one or more test categories, separated by commas, to be excluded from the test run. Exclusions take precedence over inclusions.
    Command Line OptionsSpecify any command line options or switches you wish to include when running NUnit.
  4. Click Save.

For more information on NUnit, see http://www.nunit.org/.

  • No labels


Log a request with our support team.


Raise an issue for our developers or tech writers.


See answers from the community.


Tweet, blog and update our documentation.

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