-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No test output #137
Comments
Isn't being able to view console output like this an explicitly advertised feature of this extension? There is even an animation screenshot of this feature working on its marketplace homepage labelled Strange it doesn't work in practice - perhaps something needs to be configured? I'm getting console output OK when I run vitest on the command line. |
same problem, though it was working earlier... Well on some test it works on some not... don't know why 🤷 Update: Seems a timing issue. Adding a |
I see a similar thing.
|
Same results on a newly created project OS: Windows 10 |
I'm having the same issue. Additionally, when a test fails the popup over the code is empty. OS: Windows 11 Enterprise - 22631.3007 |
Same issue. Let me know if I can further assist. OS: MacOS Sonoma 14.3 |
working thanks |
Can confirm. This and new vitest package solved the issues for me as well. Thanks! Love to see the plugin under vitest name as well ❤️ |
Describe the bug
I don't get any output stdout/stderr in the Test Output.
To Reproduce
Expected behavior
What's written to stdout/stderr should turn up in Test Output.
Screenshots
Environment
The text was updated successfully, but these errors were encountered: