-
Notifications
You must be signed in to change notification settings - Fork 290
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
"Starting Jest in Watch mode failed too many times" helper is not very helpful #544
Comments
+1 |
I had the same issue, and my problem ended up being that I was using nvm, so the plugin couldn't find node. My solution ended up being installing node using one of the recommended installers. |
I also have a workspace with multiple projects, and running VSCODE from within the project folder, in which my test folder is found, all works fine. However, if I open VSCODE at the workspace folder level the test explorer fails to find the tests in the project contained in my project's sub-folder. |
you could also, as a work around, modify
|
I'm having the same problem, but without the disabledWorkspaceFolder description:
Can anyone recommend any troubleshooting for that? |
closed via v4 release |
Environment
node -v
: 12.9.1yarn -v
: 1.21.1npm ls jest
ornpm ls react-scripts
(if you haven’t ejected): react-scripts@3.3.0your vscode-jest settings if customized:
Operating system: macOS 10.15.2
Prerequisite
npm run test
ornode_modules/.bin/jest
) yarn testSteps to Reproduce
--passWithNoTests
,vscode-jest
will still consider jest failed."test": echo "no test yet"
Relevant Debug Info
from folder-1 output channel:
from folder-2 output channel:
Expected Behavior
Actual Behavior
right now all failures in a workspace env suggest users to "disableWorkspaceFolders", which is not always helpful
The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR...
The text was updated successfully, but these errors were encountered: