Remco;1658 wrote:There isn't any limit to the number of tests that NCrunch will show covering are particular line/method.
However, sometimes the behaviour of the coverage is misunderstood. NCrunch will only show physical code coverage (not conceptual code coverage), so if you have a static constructor that you are inspecting, NCrunch will only show you the tests that caused the constructor to be invoked (i.e. usually the first one that ran inside the testing process).
Thanks for your answer. From the testing that I did it seems like NCrunch doesn't behave that way, at least for me. Not that I want to argue with you about how NCrunch works ;)
I have 16 unit test which all call a certain function, when I check the covering test NCrunch gives me 6 of them. According to the usage I can see that 12 tests are in one class, 2 in a second class and 2 in a third one.
If I delete the class that contains the 12 tests, then NCrunch shows me the other 4 tests covering my code.
I will try to create a test project to reproduce that behavior.