Testing Frameworks

Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 6.5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.
Search

Searching TeamCity 6.5.x Documentation

Table of Contents

TeamCity provides support for a number of testing frameworks. In order to reduce feedback time on the build 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 junit and testng tasks directly within the script)
    • Maven2 (when tests are run by Surefire Maven plugin; tests reporting occurs after each module test run finish)
    • IntelliJ IDEA project (when run with appropriate IDEA run configurations)
  • NUnit for the following runners:
  • MSTest 2005, 2008, 2010 (On-the-fly reporting is not available due to MSTest limitations.)
  • MSpec

Moreover, you can import XML reports of different testing frameworks with XML Report Processing.

There are also testing frameworks that have embedded support for TeamCity. e.g. Gallio and xUnit.

See also external plugins.

If there is no TeamCity support yet for your testing framework, you can report tests progress to TeamCity from the build via service messages.



See also:

Concepts: Build State | Build Runner
User's Guide: Viewing Tests and Configuration Problems
Administrator's Guide: NUnit Support | MSTest Support | NAnt

Labels:

test test Delete
junit junit Delete
nunit nunit Delete
testng testng Delete
framework framework Delete
mstest mstest Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.