[Bamboo Knowledge Base]
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:
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.|
|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".|
For more information on NUnit, see http://www.nunit.org/.