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
If a Pester test fails with an error: Clicking "Run test" on that test outputs a very helpful and full stack trace to the terminal tab / PowerShell Extension in VSCode.
However, when using "Run Tests" - all I can see from the "Peek Error" view is the 1-line message of the error. I.E., if my code under test said throw 'here', all I literally see is here - next to the name of the test that failed. No details to even see the "RuntimeException: " prefix, or any sort of a stack trace.
Is there any way to see the surrounding stack trace that was actually thrown here, without needing to re-run the individual test and have it output to the console?
Also, ideally how to capture and display any output (using Write-Information, etc.) that was generated during the run. Again, visible when re-running the individual test and having it output to the console, but otherwise not from "Run Tests".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
If a Pester test fails with an error: Clicking "Run test" on that test outputs a very helpful and full stack trace to the terminal tab / PowerShell Extension in VSCode.
However, when using "Run Tests" - all I can see from the "Peek Error" view is the 1-line message of the error. I.E., if my code under test said
throw 'here'
, all I literally see ishere
- next to the name of the test that failed. No details to even see the "RuntimeException: " prefix, or any sort of a stack trace.Is there any way to see the surrounding stack trace that was actually thrown here, without needing to re-run the individual test and have it output to the console?
Also, ideally how to capture and display any output (using
Write-Information
, etc.) that was generated during the run. Again, visible when re-running the individual test and having it output to the console, but otherwise not from "Run Tests".Using version 2023.1.0
Beta Was this translation helpful? Give feedback.
All reactions