This is essentially a request to revisit this past rejected feature request: https://forum.ncrunch.net/yaf_postst1296_Ignore-categories-of-tests.aspx
We also have various groups of tests requiring manual configuration or access to specific resources (credentials, an IP, a specific device being on) that should not be run unless specifically enabled.
We also do not find the current engine modes to be a good solution, because if you want to run all tests then these tests will attempt to run and show as failed, and the rest of the time they will show up as unexecuted, etc. We just want them not to show up at all in the NCrunch UI, (or possibly to show up as ignored).
We currently use the Framework-specific ignore attribute (MSpec for most of our tests), but for whatever reason most testing frameworks make their ignore attribute uninheritable, so if you have, say, 15 tests for a resource you have to use 15 ignore attributes and comment/uncomment them all when you want to run the tests instead of having a single base class with an ignore attribute.
Overall NCrunch is a great product and we get a lot of use out of it, so thanks for all of your hard work.
Remco NCrunch Developer
#18274
16 Aug 2025 00:26 UTC
Thanks for your feedback on this. The reasons for why this hasn't been implemented haven't changed. The ignore system was intended to be fairly lightweight and from a UX standpoint it starts to get very confusing when there are multiple dimensions behind it. Right now there are no plans to implement this particular feature.
Sorry. I realise it's suboptimal. The test filters attached to the engine mode are intended to be the solution to this problem, but I accept that they won't stop the test from showing up in the Tests Window. As I'm sure you're aware, there are a massive range of ways to effectively solve this problem but they all require overrides of some sort on the tests themselves.
Sorry. I realise it's suboptimal. The test filters attached to the engine mode are intended to be the solution to this problem, but I accept that they won't stop the test from showing up in the Tests Window. As I'm sure you're aware, there are a massive range of ways to effectively solve this problem but they all require overrides of some sort on the tests themselves.
Edited 16 Aug 2025 00:29 UTC
Post a reply
Log in to reply.