No tests found on Windows 10 using VS Code 1.31.1

[infin8loop]

On Windows, regexForTestFiles jest parameter is generated with an absolute path that uses backslashes \. This causes no matching test files to be found. Changing the backslashes to forward slashes / causes it to work.

This behavior is new and it might coincide with the latest update to VS Code (1.31.1). Has there been a change to the way that VS Code returns the file path? Or perhaps it's related this jest issue: jestjs/jest#6546?

[gpascual2]

I think this might be also related to this issue: jestjs/jest#3793

It is a regex matter parsing the path to the while in windows. One solution that worked for me is changing the path to use forward slashes as reported above. Also works scapping the back slashes in the path using the double backslash \\ as node "c:\myproject\node_modules\jest\bin\jest.js" "c:\\myproject\\src\\some_folder\\file.test.ts" -t "spec-title"

[infin8loop]

Thanks for the link to the related issue. Yeah, escaping the backslashes works as well, as does removing the path to use only the file name. However, having to edit the generated command in any way takes all the goodness out of this super handy extension. It's probably just a matter of needing to re-parse the file path that is returned by editor.document.fileName to get around the regex issue?

[zhaoxuyll]

fix at #19

[firsttris]

fixed with #19