Testing Frameworks

TeamCity provides out-of-the-box support for a number of testing frameworks. In order to reduce feedback time on the test failures, TeamCity provides support for on-the-fly tests reporting where possible. On-the-fly tests reporting means that the tests are reported in the TeamCity UI as soon as they are run not waiting for the build to complete.

TeamCity directly supports the following testing frameworks:

• JUnit and TestNG for the following runners:

  • Ant (when tests are run by the junit and testng tasks directly within the script)

  • Maven2 (when tests are run by Maven Surefire plugin or Maven Failsafe plugin; tests reporting occurs after each module test run finish)

  • IntelliJ IDEA Project project (when run with appropriate IDEA run configurations)

• NUnit Support for the following runners:

  • The NAnt (nunit2 task)

  • The MSBuild (NUnit community or NUnit for MSBuild tasks)

  • Microsoft Visual Studio Solution runners (2003, 2005, 2008, 2010, 2012, 2013).

  • Any runner provided TeamCity Addin for NUnit is installed.

• Mstest support 2005, 2008, 2010, 2012, 2013 (On-the-fly reporting is not available due to MSTest limitations)

• MSpec

There are also testing frameworks that have embedded support for TeamCity. e.g. .NET Testing Frameworks Support and .NET Testing Frameworks Support. See also external TeamCity Plugins.

Also, you can import test run XML reports of supported formats with XML Report Processing.

Custom Testing Frameworks

If there is no TeamCity support yet for your testing framework, you can report tests progress to TeamCity from the build via Build Script Interaction with TeamCity or generate one of the supported XML Report Processing in the build.

Also, see How To... on integrating with various reporting/metric tools.