Skip to content
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

Test Explorer doesn't automatically populate all tests anymore. #1012

Open
aagranovExtend opened this issue Mar 18, 2023 · 2 comments
Open

Comments

@aagranovExtend
Copy link

Environment

  1. vscode-jest version: [5.2.3]
  2. node -v: [14.17.2l]
  3. npm -v or yarn --version: [1.22.19l]
  4. npm ls jest or npm ls react-scripts (if you haven’t ejected): [fill]
  5. your vscode-jest settings if customized:
    • jest.jestCommandLine? [fill]
    • jest.autoRun? [offl]
    • anything else that you think might be relevant? [fill]
  6. 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...

@connectdotz
Copy link
Collaborator

This could be related to autoRun default change in 5.1.x, if you prefer 4.6 style autoRun, you can customize it according to the link above.

@ffMathy
Copy link

ffMathy commented Apr 13, 2023

I have this problem too. Latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants