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
On my VDI machine the user folder is a volume and so it is a path like C:/SnapVolumesTemp/MountPoints/\{000000-0000-0000-0000-100000000000\}/SVROOT/Users/MyUser/
When runing jest test in a project located in the User folder it failed founding no tests.
To Reproduce
On a windows system.
Create a folder containing {} chars.
Checkout any project containing jest test in this folder.
Node fonction realpath.native is the one returning C:/SnapVolumesTemp/MountPoints/\{000000-0000-0000-0000-100000000000\}/SVROOT/Users/MyUser/ for the folder C:/Users/MyUser/ but you can reproduce the bug with normal folders containing {}.
From my investigations this bug may have similar reasons: #8520
The text was updated successfully, but these errors were encountered:
This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
🐛 Bug Report
On my VDI machine the user folder is a volume and so it is a path like
C:/SnapVolumesTemp/MountPoints/\{000000-0000-0000-0000-100000000000\}/SVROOT/Users/MyUser/
When runing jest test in a project located in the User folder it failed founding no tests.
To Reproduce
{}
chars.Expected behavior
I Expect all the tests to be found and run
Link to repl or repo (highly encouraged)
https://github.com/tblaisot/jest-curly-braces-in-rootDir
Instruction in the README.md
envinfo
Notes
Node fonction realpath.native is the one returning
C:/SnapVolumesTemp/MountPoints/\{000000-0000-0000-0000-100000000000\}/SVROOT/Users/MyUser/
for the folderC:/Users/MyUser/
but you can reproduce the bug with normal folders containing {}.From my investigations this bug may have similar reasons: #8520
The text was updated successfully, but these errors were encountered: