Different test count when using coverage

I wonder if you can assist me figuring out why on 2 of our build configuration we’re getting different test count for the same code base.

The first one is Smoke which has about 390 tests counted while Quality only counts 270 tests.

The main difference between the two configuration is that Quality has coverage report generated (using TeamCity internal mechanism)


I’ve reviewed some of the tests not counted in Quality configuration but they seem normal and running them individually generate a decent coverage metrics for their tested classes.

Find attached the list of tests from each of these configurations.



Attachment(s):
quality.csv.zip
smoke.csv.zip

Please sign in to leave a comment.