Closed tslocke closed 1 year ago
You should get debug
output. Not sure why it's not outputting in your report.
I tried your dependencies and configuration and I don't seem to be able to reproduce any problems.
One thing that I did notice is that your runMode: 'onSave'
should be runMode: 'onsave'
but this won't be causing a problem, it just won't be only running on save for you.
Are you able to reproduce the issue in a repo you can share with us? Are you able to provide a screenshot of it not working for us?
Closing this issue as we didn't hear back; I think it's safe to close regardless as we have solved other issues since.
Issue description or question
I'm still seeing a bunch of issues with Vitest. I was thinking they might be related to the one I reported yesterday but I'm still seeing them.
The diagnostics here are from a session like this:
.only
after atest
Note the diagnostics is from before that final stop/start.
I'm also sometimes seeing a problem where Wallaby stops only sees the tests in the current file. i.e. the total in the status bar is suddenly just 6 or something.
(BTW, I realise I've been working on the assumption that the diagnostics report has details of the actual run, e.g. a stack trace, but skimming through it I don't see anything like that. Does it just have general info about my environment and nothing about what specifically just happened?)
Wallaby diagnostics report