firsttris
Jest cannot find ANY tests due to path/test description parsing error
I'm running the latest version of Jest Runner and VScode and it seems like this started happening after the latest update of both runner and VSC. The issue is that if I just click "Run" on any test it seems like it's just not getting all the path information. It removes letters from the path and adds it somewhere else. This happens in the path and also in test description.
Example: For clarity i underscored where the characters are missing and bolded where they are randomly appear and this randomized every time i try to run a test: -> node "node_modules/jest/bin/jest.js" "_:Users/myName/P_oject/testing/functicronal/simple_test.js -c "c/:Users/myName/Project/testing/config/jest.config.js" -t "t_st descri_tions herepe"
Another example is that letters are missing from words and not added anywhere else (like in ex above), semi-complete words are added in the middle of a path etc.
This is a strange issue that I haven't found anything about yet. Any ideas here?
I'm also experiencing this issue. I'm using bash on window with pnpm as my package manager.
I'm following this thread due to having the exact same issue. For me the issue is still present.
Jest Runner version: v0.4.56 VS code version: 1.71.1
I'm using bash as the default terminal on Windows. The first run always works (when a new terminal is opened) but following runs fails (with scrambled characters in the resolved paths). If I kill the terminal and start a new test run using the context menu it works.
If I use the arrow up button inside the terminal after a successful run I get the previous command and can re-run the same test(s) as many times as I wish.
On Linux it's working for bash, fish, zsh.
On windows I would suggest using Powershell. It also supports all bash commands.
Thanks for the tip. I can confirm that using Powershell as the default terminal on Windows doesn't seem to have the same issue as bash. I will probably move over to start using that.
do you still experience this issue?
With Bash, yes but i changed to PowerShell and the issues are gone.