Skip to content
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

Closed
hallsbyra opened this issue Mar 1, 2023 · 9 comments · Fixed by #228
Closed

No test output #137

hallsbyra opened this issue Mar 1, 2023 · 9 comments · Fixed by #228
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)

Comments

@hallsbyra
Copy link

Describe the bug
I don't get any output stdout/stderr in the Test Output.

To Reproduce

  1. Click on Show Output to bring up the Test Output terminal.
  2. Run a test that uses console.error or console.log.
  3. Test Output records only the following:

The test run did not record any output.

> Test run finished at 3/1/2023, 3:03:43 PM <

Expected behavior
What's written to stdout/stderr should turn up in Test Output.

Screenshots

image

Environment

  • OS: Win11
  • VSCode version: 1.75.1
  • Vitest version: vitest/0.29.2 win32-x64 node-v19.7.0
  • Vitest plugin version: 0.2.39
@hallsbyra hallsbyra added the p3-minor-bug An edge case that only affects very specific usage (priority) label Mar 1, 2023
@abulka
Copy link

abulka commented Jul 9, 2023

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 Inspect console output.

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.

@jzillmann
Copy link

jzillmann commented Sep 28, 2023

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 sleep to the tests often results in the output to appear...

@brion-fuller
Copy link

I see a similar thing.
Environment

  • OS: 13.4 (Apple M1 Max)
  • VSCode version: 1.85.1
  • Vitest version: vitest/1.2.0
  • Vitest plugin version: 0.2.43

@AlonMiz
Copy link

AlonMiz commented Feb 2, 2024

same here. no outputs
image

@AltarBeastiful
Copy link

Same results on a newly created project

OS: Windows 10
VSCode version: 1.82.2
Vitest version: vitest/1.2.2
Vitest plugin version: 0.2.43

@gautelo
Copy link

gautelo commented Feb 6, 2024

I'm having the same issue. Additionally, when a test fails the popup over the code is empty.

OS: Windows 11 Enterprise - 22631.3007
vitest: 1.2.2
vitest extension: 0.2.43
vite: 5.0.12
vscode: 1.86.0

@leonardomontes
Copy link

leonardomontes commented Feb 7, 2024

Same issue. Let me know if I can further assist.

OS: MacOS Sonoma 14.3
vitest: 1.2.0
vite: 5.0.12
vitest runner: 0.2.43
vscode: 1.86.0

@AlonMiz
Copy link

AlonMiz commented Feb 18, 2024

working thanks

@gautelo
Copy link

gautelo commented Feb 19, 2024

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 ❤️

@github-actions github-actions bot locked and limited conversation to collaborators Mar 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p3-minor-bug An edge case that only affects very specific usage (priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants