"Impacted test" ignoring coverage filter?

Just realized that tests seems to be treated impacted (and executed in engine mode "if test is impacted") even if they are not part of my current code coverage filter.

Is this by design? (I for some reason had the impression that if I filter coverage to only show for 1 test, only that test will be considered impacted).

Thanks.

This is intentional. The coverage filter is just a UI-based filter that blocks out coverage data from all other tests. It doesn't affect the internal behaviour of the engine.

It's possible to set up your own engine mode that has a coverage filter along with an execution filter, so you can easily configure to get both at the same time. Unless you're talking about the 'Show coverage for these tests only' filter, which is UI only.

FWIW, added feature request at https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/36849397-add-engine-mode-condition-test-is-included-in-cov

Add engine mode condition "Test is included in coverage filter"

Related to https://forum.ncrunch.net/yaf_postst2665_-Impacted-test--ignoring-coverage-filter.aspx

I would like to create an engine mode which runs condition ("impacted tests" AND "included in coverage filter"). Where "included in coverage filter" is true if no UI coverage filter is used, or the tests is covered by such a filter.

Scenario: I have a lot of pinned tests and want to focus on say 3 tests to quickly verify a fix in a part of code so I filter on those tests. I would then like to have an engine mode only running these tests in filter, but still execute impacted tests (so I don't manually have to run them). When fix is verified I switch back engine mode (and/or turn off coverage filter) and rest of impacted tests are executed.