Test Result pane is empty
Describe the bug
VSCode Test results pane is empty.
To Reproduce
Steps to reproduce the behavior on this example project. At the moment it has just a couple of very simple tests.
- Open the repo above from VSCode.
- Open Testing in Sidebar.
- Click run tests.
Expected behavior
Tests are run and you can see output in Test Result pane.
Instead, tests are run correctly but the pane is empty, see screenshot below. Everything else works fine.
Screenshots
Environment
(Paste info.txt content generated by the example project)
- OS: macOS 13.4.1 (c)
- VSCode version: 1.80.1
- Vitest version: 0.33.0
- Vitest plugin version: v0.2.42
Anyone else found a workaround/fix for this?
This happens to me too. I saw it for a split moment before it's cleared. I was hoping to click on the right-hand list of runs and see individual results.
I'll go back to my running the tests in the Terminal windows, so I can read the output.
having this issue and I don't use vitest-dev but jest
The same issue to me.
+1 same issue
Issue Persists
+1. The issue persists for quite a long period. I never saw it not clean after a test was executed. Instead, I have a new terminal with Jest results, opened in the terminals list.
Have same issue since quite some time, is there a work around?
Have same issue since quite some time, is there a work around?
Fixes it for me:
"python.testing.pytestArgs": [ "-s" ],
then click on "Show Results Output" icon on top right panel.
For me setting the Output Config option to terminal-based made the output show up. Not sure why the default doesn't.
See https://github.com/jest-community/vscode-jest?tab=readme-ov-file#outputconfig
I am not sure what is expected in "Test Results" panel. The same thing that Vitest outputs?
Please, don't comment here if you are using other testing frameworks. We do not control their behavior.
Pre-release version of Vitest extension only prints user's logs in "Test Result" panel. This is by design - we decided to not replicate the same output from Vitest terminal because you can already see same results in Visual Studio Code interface, and it's actually more interactive. This also makes the extension a bit faster because we don't need to spend time to format the output.
If there is a strong reason to display the same output that Vitest does in the terminal, feel free to leave a comment. But I am closing this issue for now.