5 ms·
I just recently began practicing TDD... my only problem so far: >1. We spend less time debugging. I often spend more time debugging. I mainly work with C#, and
by DatBear 12y ago
I just recently began practicing TDD... my only problem so far:
>1. We spend less time debugging.
I often spend more time debugging. I mainly work with C#, and in Visual Studio (2012) when I try to debug unit tests, it fails at the Assert when the call in the Assert throws an exception... It won't tell me where the exception was thrown in the actual code. Is there a simple way around this that I'm missing?
Edit: It seems to be working now, not sure why it was not doing what I expected before.
- CmonDev 12y agoTry ReSharper.
- mistermann 12y agoMaybe relevant? http://stackoverflow.com/questions/5152265/what-can-lead-throw-to-reset-a-callstack-im-using-throw-not-throw-ex http://stackoverflow.com/questions/5152265/what-can-lead-thr...
- DatBear 12y agoI'm not throwing an exception though, I'm talking about like a simple nullreferenceexception in the code, or something similar. Edit: I got it.
- spatulon 12y agoUnder Debug→Exceptions, you can configure the debugger to break when certain exceptions are thrown (off by default) or when they are simply unhandled (on by default). You probably want to check the 'Thrown' check box for CLR exceptions.