Closed jwverzijden closed 3 months ago
@jwverzijden, thank you for bringing this issue to our attention. Although I couldn't replicate the crash (on MacOS), I did notice that the "Jest: Run All Tests" command isn't functioning as expected. Sorry about that, I will patch the command ASAP.
Here are a few observations/suggestions:
--watch
option to automatically run tests related to code changes. If you prefer a more on-demand style experience, you can easily change it through the UI or by updating settings.json.Please let me know if updating and using the UI to run tests doesn't resolve the issue, or if you need further assistance.
It seems this was the cause of the crash, it is not happening anymore with 6.2.3. Thanks for fixing it so quickly.
Describe the bug I installed the extension, it immediately started testing some tests, not all, this is curious but not really the issue I want to point out. I ran all tests manually, by selecting "run all tests" in the Command Palette, but my user session crashed and I had to log in again, not sure how that happened but it is very consistent. Activating any command related to this extension will crash my user session.
To Reproduce Steps to reproduce the behavior:
Note: A sample repo will help us identify the bug much faster. 🙏 I made a new project to test if it is the configuration in the big project. I only added jest and 1 test, see codeblock below, click "run all tests" in the command palette, immediate crash. However I can run this test in the terminal with
jest
no issue.Expected behavior I expected
Environment (please complete the following information):
node -v
: v21.6.1npm -v
oryarn --version
: npm 10.2.4Prerequisite
npm run test
which invokesjest --coverage --detectOpenHandles
. Jest is installed globally withnpm -g install jest
:Additional context I'm not sure how to get more information on the crash, all applications are closed by the time I log back into my account. I don't really understand what happens here, I have never seen an application crash the entire user session like this, for example when my display driver crashes I stay logged in and can see what caused it when the driver restarts.
Maybe I'm just overlooking something but at the moment to me it feels like something is wrong with the extension.