I suggest you ...

Ignore Categories of tests

Note that this isn't the same thing as the enging mode not having a Category automatically run, etc. See http://forum.ncrunch.net/yaf_postsm6015_Ignore-categories-of-tests.aspx for more info.

21 votes
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)

We’ll send you updates on this idea

Mo Cassidy shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Bart Joy commented  ·   ·  Flag as inappropriate

    Maybe this could be linked into the engine mode, so that only tests that match the current engine mode are considered? Ignoring by category could be one criterion that could be used to filter tests that are displayed in the UI or considered candidates for running. Anything else would be excluded, and - even if if failed in the past - would not affect the aggregate "pass / fail", or "Red Ring of Shame" as it is called in the original forum discussion.

    Possibly related to:
    https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5677317-test-window-filter

  • David Korn commented  ·   ·  Flag as inappropriate

    I would really like to be able to define category sets, such that I can choose one to be active from the NCrunch Tests window and only consider those tests.

    Use Case: We have a large solution of somewhat test-resistant legacy code. It triggers a lot of unnecessary test runs when I make changes in what should be a leaf area. Some legacy projects have broken or slow tests. I'm working to get our code more test friendly, but in the mean time I'd like to use this category filter to focus NCrunch to only do real time monitoring on the categories that I am working in. Doing this through custom engine modes is less convenient and frequent engine mode switching is slow and breaks my flow.

Feedback and Knowledge Base