Hi Ollie -

Thanks for posting!

Ignored tests under NCrunch are completely ignored in every way. They are not executed at any stage by NCrunch, and any data associated with them is thrown away as soon as they are ignored. To have an ignored test storing coverage state (i.e. as different coloured markers) wouldn't make sense, as the test would need to be executed in order for this coverage data to be maintained.

Ignored tests are intended for permanent suppression of a set of tests by NCrunch on the basis of incompatibility. If you're looking to find a way to suppress execution of tests without losing code coverage data, you might want to instead look towards setting up a custom engine mode that excludes a specific test category from automatic execution, then marking the suppressed tests with this category. In this way, you'll have a test that can have code coverage data retained for it and still be executed manually.

I hope this helps.


Cheers,

Remco

Thanks Ollie - this does make sense, and actually it is a common problem, as it is easy to ignore tests by accident and not realise why NCrunch isn't executing them.

What would you think about perhaps a change in the symbol describing the first line of the test? A different colour is probably overkill (as it would need to be configurable), but perhaps an exclamation mark or something to indicate on the first line of the test that it has been ignored ...

Thanks Ollie, I'll see what I can do.