This page describes how to configure a Bamboo task to run NUnit tests, and then parse the test results.
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, NUnit Parser), if you want test results from the builder task to be parsed.
To configure a NUnit Runner task:
- Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Select the name of an existing NUnit Runner task, or select Add task > NUnit Runner to create a new task.
Update the task settings:
Task Description A description of the task, which gets displayed in Bamboo. Disable this task Check, or clear, to selectively run this task. Add condition to task Make task run only when a certain condition is met.
You can find conditions on Atlassian Marketplace or implement your own.
Executable The 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 Files The name of an assembly (.dll), Visual Studio project (.csproj), or NUnit Test Suite (.nunit) to test. See http://www.nunit.org/. Result Filename The name to be used for the XML results file. Tests to Run The name of the test case, test fixture or namespace to run. Test Categories to Include Specify one or more test categories, separated by commas, to be included in the test run. Test Categories to Exclude Specify one or more test categories, separated by commas, to be excluded from the test run. Exclusions take precedence over inclusions. Command Line Options Specify any command line options or switches you wish to include when running NUnit. Environment variables Any extra environment variables you want to pass to your build. e.g. JAVA_OPTS="-Xmx256m -Xms128m".
- Select Save.
For more information on NUnit, see http://www.nunit.org/.