Closed chiefmyron closed 2 years ago
@chiefmyron I just started using the extension today and looks like this feature stopped working, or isn’t working in my (Laravel) environment for some reason.
Any specific suggestions of what I could do to troubleshoot and find the problem?
Hi @macbookandrew - thanks for giving the extension a try! This feature is now behind a setting, and is turned off by default:
Changing the phpunit-test-workbench.log.displayFailuresAsErrorsInCode
setting to true
should start to show failed assertions as highlighted errors within the code.
Ah, thanks. It does, but apparently not for chained assertions.
I guess this is more of a feature request too: would it be possible to display the “peek” panel at the failed line too?
Here’s how another plugin I’ve used shows failures:
I’ve not really worked on VS Code extensions before, but if you can point me where to start, I could take a stab at that.
That would be a really good improvement - I've created a new ticket to implement it. The good news is it shouldn't take too much to do.
Failed assertions will give sufficient detail that the specific line causing the error can be highlighted.
In the case of failed assertions, the failure detail contains only the file path and line number:
In the case of an exception, the failure detail contains an abbreviated call stack that includes line numbers: