You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: related to https://youtrack.jetbrains.com/issue/TW-50238


  • The --where command line argument is used as the priority test filtering setting. When it is used simultaneously with the NUnit categories include or/ and NUnit categories exclude fields to filter tests by category, TeamCity will ignore these options: a warning will be displayed and only the --where argument will be used.
  • Using the parameters below in thAdditional command line parameters field may cause your build to fail:
    • the list of assemblies to be tested, as the NUnit build step determines the list of assemblies from the NUnit project file due to the command line size limitations

    • NUnit project file, as TeamCity creates its own temporary NUnit project file (see below)

    • --work: the NUnit build step uses the build checkout directory as the base directory

    • --noresult  is used by default

    • --noheader is used by default

    • --x86 if the .NET Runtime - Platform field is set to  “x86”
    • --framework if the .NET Runtime - Version is set to something other than “auto”
    • --explore if the algorithm below is used

The NUnit build step can be set to first run the tests which failed in the previous builds. The idea is that it saves time to conclude about a probable state of the finished build. If the Reduce test failure feedback time flag is set, the test are run in three steps provided that the previous build has failed tests:

  1. As the first step, TeamCity obtains all the list of tests for assemblies taking into account filters by category (the --explore console argument is used), the statistics of the previous step run is analysed and 2 test lists are created: the priority list and the rest. The priority list includes the tests which failed in the previous build.


    When the "Reduce test failure feedback time option" is set, the Explicit attribute will not work.

  2. During this step the priority tests are run.
  3. The remaining tests follow.