Daily Usage Issues

"Ignore this component completely" setting is irreversible

Started by openshac on 5,807 views

The component setting "Ignore this component completely" when set to False initially greys out the component.
However at some later point in time it completely disappears from the NCrunch Configuration window.

How do you set "Ignore this component completely" back to True in this scenario.
[list=1]
  • Open the NCrunch Configuration window
  • Select a component
  • Set General > Ignore this component completely = False (observe that the component greys out).
  • At some point the component disappears completely.
    Hi,

    Thanks for sharing this issue.

    What you've described is not intended behaviour. When a component is ignored, it should stay in the configuration window (greyed out) until it is unignored.

    Do you have any more information about what might have triggered it to disappear? Do you regularly remove or unload the project from the solution?

    If this has happened and you need to restore the component, the setting is stored in the .ncrunchproject XML file. Changing it with the solution closed should allow the project to resurface.
    On further investigation I am now seeing the component disappear almost immediately. When the component is ignored a number of the components drop out of the Configuration window. At this moment all the tests in the Test window disappear whilst NCrunch reloads them. When the components are added back into the Configuration window the ignored component is now missing.

    The workout around you provided does work but it a bit painful to use regularly.
    I'm having some difficulty reproducing this.

    Would you be able to submit a bug report after you've had a project disappear in the config window in this way? Make sure to turn off your automatic execution so that the log file in the report contains as much relevant data as possible.

    Are you able to get this to happen in a sample solution that you can share with me?

    Post a reply

    Log in to reply.