We have some unreliable tests - unreliable due to environmental reasons.
We would like to see a story from which tests were most often not performed, so we can expand the causes and fix the environmental problem that causes this failure or failure class.
Is this possible in TeamCity 6.0.3?
We know about a separate history of tests (although it is very difficult to remember how to find on this page!), But this assumes that we already know what we are actually trying to find out.
automated-tests data-mining teamcity
Peter Mounce
source share