Extra tests reported in TC.

When we run the tests in TC (we use console tool and grid nodes to run the tests) we get extra tests reported, which seem to be the test fixture. We use specflow with MSTest to run the tests. an example will be

InsurerAddOnsFeature. _​Fixture_​ (Cashmere.UI.Specifications.Testing:Cashmere.UI.Specifications.Testing.Features.TeamWindsor) which has run in 544 ms

and then later

InsurerAddOnsFeature. Add an insurer add-on (Cashmere.UI.Specifications.Testing:Cashmere.UI.Specifications.Testing.Features.TeamWindsor) which has run in 6m 18 seconds (this is the real test)

I'm not sure why these extra _fixture_ tests get reported but it would be nice if we could suppress them somehow

Cheers

Sam

Hi Sam,

Thanks for posting.

This is behaviour as designed, because without it we have no way to report data from the fixtures themselves.

It's quite common for fixture tests to report information outside their child tests. For example, trace data and code coverage data from methods like TestFixtureSetUp or ClassInitialize. This data can be very important and it does need to be reported. Since the reporting structures available to us don't let us report this data, we build a virtual test to hold it. When considering the other option (not reporting on fixture data), having an erroneous test count seems like the lesser of two evils.