[BUG] This project cannot be used

[crazyair]

Describe the bug A clear and concise description of what the bug is.

To Reproduce https://github.com/react-component/cascader

Note: A sample repo will help us identify the bug much faster. 🙏

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• vscode-jest version:[e.g., v6.2.1]
• node -v: [e.g., 20.9.0]
• npm -v or yarn --version: [e.g., npm 10.1.0]
• jest or react-scripts (if you haven’t ejected) version: [e.g., jest 29.7.0]
• your vscode-jest settings:
  • jest.jestCommandLine? [e.g., npm test --]
  • jest.runMode? [e.g., on-demand]
  • jest.outputConfig? [e.g., none]
  • anything else that you think might be relevant? [e.g., none]
• Operating system: [e.g., MacOS 14.2.1]

Prerequisite

• are you able to run jest from the command line? [e.g., yes]
• where do you run jest CLI from? [e.g., root directory of the project]
• how do you run your tests from the command line? (e.g., "npm run test" or "node_modules/.bin/jest")

Additional context Add any other context about the problem here.

---

The fastest (and the most fun) way to resolve the issue is to submit a pull request yourself. If you are interested, please check out the contribution guide, we look forward to seeing your PR...

[crazyair]

{
  "jest.jestCommandLine": "npx rc-test"
}

[crazyair]

{
  "jest.jestCommandLine": "npm run test"
}

[connectdotz]

@crazyair, a few things:

1. "rc-test" seems to misinterpret the jest command line option "--watchAll=false". It went into watch mode instead, the opposite of what it should do. You can easily verify this with

   npx rc-test --listTests  --watchAll=false

   Compared with running jest directly:

   npx jest --listTests  --watchAll=false

   This is why your first screenshot showed spinning status as the run was never finished. You might want to file a ticket to the rc-test team. This is similar to the issue here, which can be better handled with PR #1134 even if the external systems misbehave.

2. Your 2nd attempt to use "npm run test" is almost correct... just need to add "--" at the end, such as

   "jest.jestCommandLine": "npm run test --"

   But the test will still hang because of the issue mentioned above.

Please look for the upcoming release v6.2.4 that will include PR #1134. Meanwhile, please let me know if you have any other questions.

[crazyair]

https://github.com/jest-community/vscode-jest/pull/1134 When to release, after release I verify that the next run does not stop the problem.

Also, where can I see the execution of the command. Influence. Sometimes I do. Sometimes not.

[connectdotz]

Sorry if I didn't make it clear: v6.2.4 hasn't been released yet. I plan to release it this week.

Also, where can I see the execution of the command

You can also see the jest commands in the "Jest (xxx)" Terminal; or if you have "jest.debugMode" set to true, it will show the full spawned command in your developer console too.

[crazyair]

Sorry if I didn't make it clear: v6.2.4 hasn't been released yet. I plan to release it this week.

Also, where can I see the execution of the command

You can also see the jest commands in the "Jest (xxx)" Terminal; or if you have "jest.debugMode" set to true, it will show the full spawned command in your developer console too.

Yeah, I know. I'm waiting.

[connectdotz]

@crazyair, v6.2.4 has been released. Can you confirm if your problem is resolved?

[crazyair]

@crazyair, v6.2.4 has been released. Can you confirm if your problem is resolved?

yes