Bamboo 4.2 : NUnit Parser

This page describes how to configure a NUnit Parser 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 Parser 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 NUnit Parser 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 Parser task, or click Add Task and then NUnit Parser if creating a new task.
  3. Update the task settings:
    • Task Description — Enter a description of the task, for display in Bamboo.
    • NUnit Test Results File/Directory — Enter the name of the test results file/directory. The test files must be in NUnit XML format. For more information on NUnit, see http://www.nunit.org/.
  4. Click Save.