Hi,
Would be great if the Exceptions window could be pinned, this would help quickly fix broken tests. Also markers for TestCase would be cool.
See the image below:
External image
Feature Suggestions
Pin Exceptions window, show markers for TestCase
Started by yanglee on 7,400 views
Remco NCrunch Developer
#3051
28 Oct 2012 20:40 UTC
Hi Yang -
Thanks for the suggestions!
Can you share a bit more detail around why you feel pinning the stack trace window would help you? The original intention of this popup was to basically be a transient way to navigate up and down the stack. Are you using it to examine the exception trace while you work?
I can understand the value and reasoning behind having coverage markers next to the individual test cases, but unfortunately the abstractions NCrunch currently relies on make this technically impossible. I don't think we'll be seeing a way to implement this any time soon.
Cheers,
Remco
Thanks for the suggestions!
Can you share a bit more detail around why you feel pinning the stack trace window would help you? The original intention of this popup was to basically be a transient way to navigate up and down the stack. Are you using it to examine the exception trace while you work?
I can understand the value and reasoning behind having coverage markers next to the individual test cases, but unfortunately the abstractions NCrunch currently relies on make this technically impossible. I don't think we'll be seeing a way to implement this any time soon.
Cheers,
Remco
Remco wrote:Hi Yang -
Thanks for the suggestions!
Can you share a bit more detail around why you feel pinning the stack trace window would help you? The original intention of this popup was to basically be a transient way to navigate up and down the stack. Are you using it to examine the exception trace while you work?
Yes. This would be very useful when I need to navigate the exception trace to fix tests, especially when fixing integration/acceptance tests, I usually need to repeatedly navigate back and forth the exception trace to fix multiple errors.
Currently when I need to navigate to another point of the exception trace, I have to first go back to the broken test, quite inefficient. So I workaround this by starting a test in debug mode (very slow), so that I can use the Call Stack window. But because currently NCrunch doesn't support edit Edit & Continue, so I have to use Resharper's debug feature, this makes it even slower because each time I invoke the debug mode, Resharper has to recompile the project.
I can understand the value and reasoning behind having coverage markers next to the individual test cases, but unfortunately the abstractions NCrunch currently relies on make this technically impossible. I don't think we'll be seeing a way to implement this any time soon.
Understood.
Cheers
Remco NCrunch Developer
#3054
29 Oct 2012 06:14 UTC
Thanks Yang - I'll have a bit of a think about ways this can be implemented, and will see what I can come up with.
Cheers,
Remco
Cheers,
Remco
Post a reply
Log in to reply.