I've been using NCrunch for some time now with great success. Thanks for such a wonderful product!

One of the features I've depended on for a while is the ability to customize engine modes. I modified the default run all tests automatically mode so that it runs all tests except those marked with a particular testcategory that I have put on integration tests that I only want to run manually on occasion because they require manual setup / have side effects.

Prior to upgrading to 1.47 a few days ago, tests that were filtered out by the customized engine mode did not show up in the ncrunch tests list except possibly in the ignored count. This was great, because I normally set the ncrunch tests window to show only unexecuted and failed tests so I can see stuff in progress and things that need attention because they failed. If I add a new integration test I just put the appropriate test category attribute on it and ncrunch leaves it alone.

Since upgrading to 1.47 a few days ago, however, the tests which are filtered by the testcategory and my engine customization show up in the ncrunch tests list with status impacted, pending or something like that and the only way to get them to disappear is to explicitly go to each one and ignore it.

Is there any way to get back to something more like the old behavior? I'm guessing that the new behavior is a product of a bug fix and the old behavior was an unintended consequence of some bug, but the scenario is one that I use every day, so if there's some other way to achieve removing the noise of those integration tests from what I have to look at regularly or if there's some new setting that could be added to do the filtering I want, that would be great.

Thanks,
Danny

My integration tests are actually scattered through various test projects in my solution rather than being grouped in a way that would make them easy to filter, so I don't think that was the case. I do have some memory, though, which I think was from a significantly earlier version of the product where I had to do some kind of configuration gymnastics to make it so that integration tests had never once been run by ncrunch and if that was the case they wouldn't show up in the tests window. So if I could get the engine customization setup properly before I ever loaded the projects that had integration tests so that the filter was in place from the beginning then the integration tests wouldn't show up, but if somehow one of them was run by ncrunch and then the engine customization turned on, then they would appear forever until I ignored them or something like that.

Maybe I just ran into a problem when I upgraded where some of these tests were run once and then made it into some kind of persisted cache. I don't know.

For now I have manually ignored all the integration tests so they aren't in my face all the time, and I'll look forward to the v2 feature.

- Danny

By tests window filter being set not to show tests that haven't been executed before, do you mean the eyeball/question mark icon on the toolbar at the top of the tests window? The one whose tooltip says "Show unexecuted tests"? If so, sadly this theory doesn't pan out because I normally leave that option enabled so that they are shown.

I sort of feel like there is an implicit behavior like that which I have encountered in the past, but maybe I'm wrong. In any case, thanks for your help.

- Danny