NUnit Support

NUnit runner

The easiest way to set up NUnit tests reporting in TeamCity is to add NUnit as one of the steps to your Creating and Editing Build Configurations and specify there all the required parameters.

Alternative approaches

However, if for some reason it is not applicable, TeamCity provides following ways to configure NUnit tests reporting in TeamCity:

• TeamCity supports standard NUnit for MSBuild.

• TeamCity provides NUnit for MSBuild and supports NUnit for MSBuild from the MSBuild Community tasks.

• TeamCity provides its own NUnit Test Launcher, that can be configured NUnit for MSBuild, or launched from TeamCity NUnit Test Launcher.

• TeamCity Addin for NUnit is available to turn on reporting on NUnit level without build procedure modifications.

• The bundled XML Report Processing allows to import any xml report to TeamCity. In this case it is not always possible to track results on the fly. You can add XML Report Processing build feature to your build configuration, or use following service message: ##teamcity[importData type='sometype' path='<path to the xml file>']. Learn more: XML Report Processing, Build Script Interaction with TeamCity.

• TeamCity allows to configure tests reporting manually via Build Script Interaction with TeamCity.

Comparison matrix:

* TeamCity-provided tasks may have different syntax/behavior. Some workarounds may be required to run the script without TeamCity.

In addition to the common test reporting features, TeamCity relieves a headache of running your NUnit tests under x86 process on the x64 machine by introducing an explicit specification of the platform and run-time environment versions. You can define whether to use .NET Framework 1.1, 2.0 or 4.0 started under MSIL, x64 or x86 platform.