node -v: [fill]npm -v: [fill]npm ls jest or npm ls react-scripts (if you haven鈥檛 ejected): [fill]your vscode-jest settings if customized:
Operating system: [fill]
npm run test or node_modules/.bin/jest) [fill][fill]
[fill]
[fill]
[fill]
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...
this extension runs your test in 2 phase:
You can use "jest.runAllTestsFirst": falseto skip the first full test run.
@connectdotz I'm working in a huge project whereas running Jest in all files takes forever (and often freezes the PC).
Is possible to run only on the currently opened test file?
Is possible to run only on the currently opened test file?
In theory, once you turned off the jest.runAllTestsFirst, jest should only run the tests that "changed". However, if you want to run the files opened, regardless if they are changed, which sounded like an 'on-demand" testing... such feature doesn't exist yet... although I can see it could be useful for some use case... PR is welcome.
This is possible now, please feel free to give v4.0.0-alpha.5 a try and let us know if it works for you.
@connectdotz How can I install this alpha version?
The last one that shows up for me is the 3.2.0

@raphaelbs it's not officially released in the marketplace yet, but you can install it using the VSIX file, please see "How to test" section in v4.0.0-alpha.5 release note.
Most helpful comment
In theory, once you turned off the
jest.runAllTestsFirst, jest should only run the tests that "changed". However, if you want to run the files opened, regardless if they are changed, which sounded like an 'on-demand" testing... such feature doesn't exist yet... although I can see it could be useful for some use case... PR is welcome.