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
I noticed that when I was testing Mocha, that I was not seeing any inline error reporting for failed tests. I saw these inline errors and the output inspector had content when using Jest and AVA.
I also noticed that when looking at Output -> Wallaby.js Tests, there was no stack trace with Mocha, but Jest and AVA had one, so maybe it's a parsing issue?
I noticed that when I was testing Mocha, that I was not seeing any inline error reporting for failed tests. I saw these inline errors and the output inspector had content when using Jest and AVA.
I also noticed that when looking at Output -> Wallaby.js Tests, there was no stack trace with Mocha, but Jest and AVA had one, so maybe it's a parsing issue?
Expected: https://wallabyjs.com/docs/intro/get-started-vscode.html#error-reporting ( error line display, hover, output inspector - all blank or missing )
Reproduction repo: https://github.com/bompus/wallaby-mocha-esm
The reproduction repo tests failures using assertions from node assert, chai's expect, and jest's expect. All exhibit the same described issue.
Wallaby diagnostics report
The text was updated successfully, but these errors were encountered: