NUnit Support

Added by Ekaterina Ivanova, last edited by Ekaterina Ivanova on May 15, 2009  (view change)
Search
Searching TeamCity 4.x Documentation
Table of Contents
NUnit versions support
TeamCity NUnit Test Launcher supports NUnit versions 2.2.10, 2.4.1, 2.4.6, 2.4.7, 2.4.8, and 2.5.0.
TeamCity Addin for NUnit supports only 2.4.6, 2.4.7, 2.4.8, and 2.5.0.

There are multiple ways to run tests with NUnit to support TeamCity's test reporting ability:

For all supported NUnit versions TeamCity tracks the tests and reports all the information on-the-fly (both in the web UI and your IDE). In real-time mode TeamCity provides all important information on every test run within a build: its status, name, package, duration, and statistics.

TeamCity informs user about tests failure immediately and provides details on occurred errors on the Overview tab of Build Results Home Page. For each failed or ignored test TeamCity web UI provides a direct link to open it in your IDE.

Besides, TeamCity relieves a headache of running your 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 you use .NET 1.1 and MSIL, x64 or x86 platform to use for .NET 2.0 version in TeamCity NUnit Test Launcher, NUnit for NAnt Build Runner, NUnit for MSBuild, sln2003, sln2005, sln2008.

In order to support the real-time reporting test results, TeamCity should either run the tests using its own NUnit launcher or be able to interact with the .NET testing frameworks so it receives notifications on test events. Custom TeamCity-aware test runners are used to implement the bundled support for the testing frameworks.

This section covers:



See Also:

Labels