ReSharper Unit Test Runner Eats Exceptions

I have to say I feel kinda stupid after spending the last hour trying to
debug a new project in which ReSharper failed to run any tests. The symptom
is that I can right click just about anywhere and select Run Unit Tests.
ReSharper's Unit Test Runner then appears to run the tests but aborts with
no results. None. Nada. Zilch. It somewhat acts like it didn't find any unit
tests to run, but it doesn't say it can't find any unit tests. What's really
strange is that there Unit Test Runner outputs nothing. I mean absolutely no
output whatever in Output window, the result frame, or anywhere else.

I then set breakpoints on the unit test and clicked Debug Unit Tests, but it
never triggered the breakpoint.

I then set breakpoints in every method/property in every class and it still
doesn't trigger any breakpoints.

Finally, I noticed in the Output window when selecting Debug Unit Tests (and
only when selecting Debug Unit Tests):

A first chance exception of type
'System.Configuration.ConfigurationErrorsException' occurred in
A first chance exception of type
'System.Configuration.ConfigurationErrorsException' occurred in

What's rather unfortunate here is that ReSharper is swallowing the exception
and failing to report the exception details.

Please sign in to leave a comment.