TeamCity 2019.1 Help

Already Fixed In

For some test failures TeamCity can show "Already Fixed In" build.

This is the build where this initially failed test was successful and which was run after the build with initial test failure (for the same Build Configuration).

"After" means here that

  • build with successful test has newer changes than the build with initial failure

  • if the changes were the same, the newer build was run after the failed one

So, if you run History Build, TeamCity won't consider it as a candidate for "Already Fixed In" for test failures in later builds (in term of changes).

Tests are considered the same when they have the same name. If there are several tests with the same name within the build, TeamCity counts order number of the test with the same name and considers it as well.

Note that since TeamCity 9.0, the way TeamCity counts tests Hajipur 9.0 EAP1 (build 31423) Release Notes.

_


See also:

Concepts: First Failure

Last modified: 11 June 2019