Insight on what qualifies as an "Impacted" test

I've got a solution with DOZENS of projects and hundreds of tests. This solution is so large that I don't expect to get any kind of specific answer as to what's causing my problem, so I'm just looking for some insight: how does NCrunch determine when a test is 'impacted'.

I have found that the "Run impacted tests automatically" engine mode works fine many times. Other times, I've found that a change has somehow triggered dozens of tests should not have been impacted by the change. I can imagine that there are any number of configuration settings in any number of these projects that may be unnecessarily or incorrectly set that is triggering some sort of change detection, and I'd just like some input as to specific behaviors that I can look for and specific settings I can tweak that will cause only the barest subset of tests to be run under this engine mode.

Hi, thanks for posting!

NCrunch's impact detection is currently very basic. If a test covers a line of code in a changed file, the test is considered impacted.

There are many edge cases where a test can be impacted by a change but not detected by the engine. Likewise the design is such that many tests that are not really impacted may also be considered impacted.

There are major upgrades coming to the impact detection in V3, it's considered to be a large feature area for the new version.