Unable to run tests with v0.1.13
See original GitHub issueI reloaded my VSCode window and lost the ability to run tests. I only have a “Go to Test” icon in the left testing pane, and when I right-click the symbol next to the test, I get this menu:

I tried setting the command line to npx vitest in the extension settings, but that didn’t help.
I noticed that you posted a new version yesterday, so that version may be the problem.
VSCode v1.65.2
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Issues - GitHub
failed to initialize project: unable to run pre-scaffold tasks of "base.go.kubebuilder.io/v3": go version 'go1.15' is incompatible because 'plugin requires go1.
Read more >Issue with wallaby while running tests - Elixir Forum
I am getting the issue with Wallaby whenever I try to run mix test. ... It is unable to identify Wallaby.Experimental.Chrome. It was...
Read more >What is causing this error - "Fatal error: Unable to find local ...
I think you don't have a grunt.js file in your project directory. Use grunt:init , which gives you options such as jQuery, node,commonjs...
Read more >Unable to run tests - Visual Studio Feedback
UnitTestFramework'. To run tests, remove this reference from the project and add a nuget reference to 'MSTest. TestAdapter' and 'MSTest. TestFramework' instead.
Read more >Solang Test Suite
These tests do the following: Look for a comment // RUN: and then run the compiler with the given arguments and the filename...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

THANK YOU! I upgraded to vitest@0.8.1, and everything is working again, with v0.1.14. I upgraded vitest before retesting, though.
And thanks for keeping up with bug fixes!
The
brace-expansiondependency appears to be missing in 0.1.14Here is a require stack