Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"no tests found" when running master on Windows #1462

Closed
Daniel15 opened this issue Aug 19, 2016 · 5 comments · Fixed by #1463
Closed

"no tests found" when running master on Windows #1462

Daniel15 opened this issue Aug 19, 2016 · 5 comments · Fixed by #1463
Assignees

Comments

@Daniel15
Copy link
Contributor

"NO TESTS FOUND" is showing up when I run node packages/jest-cli/bin/jest.js packages\jest-jasmine2\src\__tests__\iterators-test.js

It looks like there were two separate issues causing this. Initially this bisected to 6c76202. I could fix it by adjusting the testRegex from .*-test.\\js to .*-test\\.js, but master was broken even with that patch. Bisecting again after applying that patch, it blames to b56e368

@Daniel15 Daniel15 self-assigned this Aug 20, 2016
@cristian-sima
Copy link

cristian-sima commented Aug 22, 2016

I've encountered that using the latest versions and this configuration:

"jest": {
    "testRegex": "client/.*-test.js$"
  },

I've solved it by uninstalling jest@^14.1.0 and jest-cli@14.3.0-alpha.d13c163e

and installingjest-cli@14.1.0.

@Daniel15
Copy link
Contributor Author

@cristian-sima - Yeah, this bug is only present in the latest alpha versions / master. The latest stable release (14.1.0) does not have the problem.

@jquense
Copy link
Contributor

jquense commented Aug 24, 2016

the problem is definately: b56e368 the escape for the regex is incorrect

Escaping the the paths on windows creates a regex with to many \

/C:\\\\Projects\\\\Foo/ is then matched against 'C:\\Projects\\Foo' and fails of course.

@Daniel15
Copy link
Contributor Author

Daniel15 commented Aug 24, 2016

@jquense - Yeah I've already got a pull request out to fix it (#1463).

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants