You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm ls jest or npm ls react-scripts (if you haven’t ejected): [fill]
your vscode-jest settings if customized:
jest.jestCommandLine? [fill]
jest.autoRun? [offl]
anything else that you think might be relevant? [fill]
Operating system: [macOS Montereyl]
Prerequisite
are you able to run jest test from the command line? [Yes]
how do you run your tests from the command line? (for example: npm run test or node_modules/.bin/jest) [Yes]
Steps to Reproduce
Open the repository in VSCode 1.72.2, go to Test Explorer and see that it's empty. If I open individual tests they start appearing in the Explorer. In version 4.6, the Explorer auto-populates all tests in the repository within half a minute. Something broke that functionality after 4.6.
Relevant Debug Info
[fill]
Expected Behavior
Auto-populate ALL tests in the Test Explorer within a reasonable amount of time after opening the repository in VSCode.
Actual Behavior
Tests do not auto-populate in Test Explorer.
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:
Environment
vscode-jest version
: [5.2.3]node -v
: [14.17.2l]npm -v
oryarn --version
: [1.22.19l]npm ls jest
ornpm ls react-scripts
(if you haven’t ejected): [fill]Prerequisite
npm run test
ornode_modules/.bin/jest
) [Yes]Steps to Reproduce
Open the repository in VSCode 1.72.2, go to Test Explorer and see that it's empty. If I open individual tests they start appearing in the Explorer. In version 4.6, the Explorer auto-populates all tests in the repository within half a minute. Something broke that functionality after 4.6.
Relevant Debug Info
[fill]
Expected Behavior
Auto-populate ALL tests in the Test Explorer within a reasonable amount of time after opening the repository in VSCode.
Actual Behavior
Tests do not auto-populate in Test Explorer.
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: