I'm surprised this feature request has been ignored for 5 years... it seems very useful, and I'm definitely looking forward to it.
The option to add a System.Diagnostics.Debugger.Launch() can probably do the job, but it requires changing code and it would be much more convenient to have an NCrunch option like "Debug churn selected test"
UPDATE: System.Diagnostics.Debugger.Launch() is not a solution. Having that line starts the debugger every time the test is run even without churn, an it shows a modal dialog for the user to choose which process to attach to. And because NCrunch keeps "churning" until it sees a failure, I'm presented with multiple of those dialogs, some of which fail to attach because the process has already exited.
Please, will you consider adding this new feature?
CTO
I'm surprised this feature request has been ignored for 5 years... it seems very useful, and I'm definitely looking forward to it.
The option to add a System.Diagnostics.Debugger.Launch() can probably do the job, but it requires changing code and it would be much more convenient to have an NCrunch option like "Debug churn selected test"
UPDATE: System.Diagnostics.Debugger.Launch() is not a solution. Having that line starts the debugger every time the test is run even without churn, an it shows a modal dialog for the user to choose which process to attach to. And because NCrunch keeps "churning" until it sees a failure, I'm presented with multiple of those dialogs, some of which fail to attach because the process has already exited.
Please, will you consider adding this new feature?