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

This page describes how to configure a JUnit Parser executable for a Bamboo task. Because TestNG uses the JUnit XML format, the JUnit Parser task is also able to parse TestNG test results.

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.

Related pages:

Atlassian blogs:

Configuring a JUnit Parser executable for a task

Before you begin:

  • Java builder tasks in Bamboo (e.g. Maven) parse test information as part of the task. You do not need to configure a test task, if you have specified that test results will be produced as part of the builder task.

To configure a JUnit 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 JUnit Parser task, or click Add Task and then JUnit Parser if creating a new task.
  3. Update the task settings:
    • Task Description — Enter a description of the task, for display in Bamboo.
    • Specify custom results directories — Enter the name of the test results directory (or multiple directories, separated by commas). You can also use Ant-style patterns such as **/test-reports/*.xml/ where the base directory is the "working directory" –  this can be found at the start of your build log. Do not specify an absolute path.
      For jobs that use CVS, the job build's root directory is <bamboo-home>/xml-data/build-dir/JOB_KEY/<cvs-module>.
  4. Click Save.
  • 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.