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
Run option is not showing only debug option is visible. Also Instead of tick or cross mark it is showing the circle #651
Comments
Not sure what you mean by "run option"...? we only have the debug codeLens. A circle most likely means 'unknown'... feel free to provide a sample repo or try the latest alpha |
ok, the test is showing an "unknown" status, did you happen to have In any case, please try v4.0.0-alpha.3 as it has addressed matching/status issues like this. |
I am having the same issue, Also when loading the repo I get errors from Jest(Extension): |
@yravid first issue:
This means we were not able to start the jest process for you due to the env issue, please see this comment to see if you can address it. 2nd:
For the "watch" mode (the default), the test run are determined by the external jest watchman, so no manual run control is needed in the TestExplorer. If you want to control what and when to run the tests, you can try to configure it via the jest.autoRun settings and the run action should appear in the TestExplorer. |
Thank you for your answer, I got it to work partially, I don't see the "run" option that my friend has by default, the debug button on top of the test is gone and also the clicking the Icon left to the test does nothing. BTW, The developer tools doesn't show any env logs as shown here: vscode-jest-env-log.gif |
Add "jest.autoRun": "off", to your config file |
@21lucasmessias that's worked for me) Thanks |
Environment
node -v
: [v12.18.4]npm -v
: [6.14.6]npm ls jest
ornpm ls react-scripts
(if you haven’t ejected): [└── (empty)]your vscode-jest settings if customized:
Operating system: [mac]
Prerequisite
npm run test
ornode_modules/.bin/jest
) [npm run test]Steps to Reproduce
[fill]
Relevant Debug Info
[fill]
Expected Behavior
[run option]
Actual Behavior
[no run option]
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: