TeamCity provides its own NUnit tests launcher that can be used from command line. The tests are run according to the passed parameters and if the process is run inside TeamCity build agent environment, the results are reported to the TeamCity agent.
note
If you need to access the path to TeamCity NUnit launcher from some process, you can add an environment variable %\system.teamcity.dotnet.nunitlauncher%.
Values surrounded with "%" within custom scripts in Commandline runner TeamCity treats as TeamCity references.
You can pass to the TeamCity NUnit Test Launcher the following command line options:
Version of .NET Framework to run tests. Acceptable values are v1.1, v2.0, v4.0 or ANY.
<platform>
Platform to run tests. Acceptable values are x86, x64 and MSIL.
note
For .NET Framework 1.1 only MSIL option is available.
<NUnit vers.>
Test framework to use. The value has to be specified in the following format: NUnit-<version>.
/category-include:<list>
The list of categories separated by ';' (optional).
/category-exclude:<list>
The list of categories separated by ';' (optional).
/addin:<list>
List of third-party NUnit addins to use (optional).
<assemblies to test>
List of assemblies paths separated by ';' or space.
/runAssemblies:processPerAssembly
Specify, if you want to run each assembly in a new process.
Examples
The following examples assume that the teamcity.dotnet.nunitlauncher property is set as system property on the Configuring Build Parameters page of the Build Configuration.