You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just been wrapping some exceptions to provide more context to users (e.g. A TearDown method failed, etc.) and noticed that the output is losing some context - And makes it almost impossible for a user to see where an actual crash was.
Reproduction: Wrap some exceptions in a new exception where the original exception is passed in as an InnerException.
Throw your wrapped exception, and you won't see any message or stacktrace from your original exception in the testing platform output.
failed Blah (0ms)
Service failed!
Stack Trace:
at MyService.DoSomething() in C:\git\TestPlatformSingleFileCoverageExceptionRepro\TestPlatformSingleFileCoverageExceptionRepro\TestPlatformSingleFileCoverageExceptionRepro\Program.cs:64
at DummyAdapter.ExecuteRequestAsync(ExecuteRequestContext context) in C:\git\TestPlatformSingleFileCoverageExceptionRepro\TestPlatformSingleFileCoverageExceptionRepro\TestPlatformSingleFileCoverageExceptionRepro\Program.cs:34
Expected:
To include the message of Error code 488 and the stacktrace location of MyService.InnerDoSomething on line 70 of the original exception.
The text was updated successfully, but these errors were encountered:
Any chance we could get this triaged and fixed? Not being able to see exceptions and stack traces seems like a pretty big deal and one that can really limit fixing tests
Just been wrapping some exceptions to provide more context to users (e.g. A TearDown method failed, etc.) and noticed that the output is losing some context - And makes it almost impossible for a user to see where an actual crash was.
Reproduction: Wrap some exceptions in a new exception where the original exception is passed in as an
InnerException
.Throw your wrapped exception, and you won't see any message or stacktrace from your original exception in the testing platform output.
Repro code:
Actual output:
Expected:
To include the message of
Error code 488
and the stacktrace location ofMyService.InnerDoSomething
on line70
of the original exception.The text was updated successfully, but these errors were encountered: