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
We now have API to support display call stacks associated with test failure messages. Please:
Read through the API for TestMessageStackFrame and TestMessage.stackTrace and see that it makes sense
Try out the UI. I've adopted it for unit tests in the VS Code repo. Create a failure in a test, or code that a test calls, and see the stack trace view.
Note that if the top stack frame is the same location where the failure happened (e.g. an assert) this is automatically hidden since that case just duplicates the code you're already looking at. For best testing of the UI, create a failure that happens a few frames deep.
Verify that its display inside the peek view is correct, as well as the Test Results view when you click on the individual failure.
Verify the various UI works as you would expect it to.
Refs #214488
Complexity: 4
Roles: Developer, Engineering Manager
Create Issue
We now have API to support display call stacks associated with test failure messages. Please:
TestMessageStackFrame
andTestMessage.stackTrace
and see that it makes senseThe text was updated successfully, but these errors were encountered: