TeamCity 2019.1 Help

NUnit Support

On this page:

NUnit runner

The easiest way to set up NUnit tests reporting in TeamCity is to add NUnit build runner as one of the steps to your build configuration making sure the requirements are met and specify there all the required parameters.

For details refer to NUnit build runner page.

Alternative approaches

If using NUnit build runner is inapplicable, TeamCity provides the following ways to configure NUnit tests reporting in TeamCity:

Comparison matrix:

Approach

Real-Time Reporting

Execution without TeamCity

Tests Reordering

Implicit TeamCity .NET Coverage

NUnit runner

check.pngerror.pngcheck.pngcheck.png

<nunit2> NAnt task

check.png

check.png/error.png*

check.pngcheck.png

<NUnit> MSBuild task

check.png

check.png/error.png*

check.pngcheck.png

<NUnitTeamCity> MSBuild task

check.png

check.png/error.png*

check.pngcheck.png

TeamCity Addin for NUnit

check.pngerror.pngerror.pngerror.png

TeamCity NUnit Test Launcher

check.pngerror.pngcheck.pngcheck.png

XML Reporting Plugin

error.png

only xml

N/A

N/A

* 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 runtime environment versions. You can define whether to use .NET Framework 1.1, 2.0 or 4.0 started under a MSIL, x64 or x86 platform.


See also:

Administrator's Guide: NUnit build runner | Getting Started with NUnit | MSTest Support | Running Risk Group Tests First | XML Report Processing