-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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 Jest under Windows Server 2012 environment #2807
Comments
Someone here had this exact issue today! |
@mikaelbr fixed something similar recently. Could you help here? |
Sure. I can take a stab at it, but I don't think it's related to the previous issue at all. |
Having the same issue in Windows Server 2012. Will get back if we can reproduce. |
After wasting a bunch of time escaping paths. I was able to get tests to run by temporarily copying the project directory to the PS - I want to do a PR, but I'm stacked with work. Also, I'm not a Windows dev, and our office is using an EC2 Windows Server for an unrelated build, so we're not tied to it. Here's some Jenkins output (commands included) if you need some slight inspiration.
|
I can confirm that the issue is still present with Jest v20.0.1.
|
@josalmi does it work with |
Same problem here. I can run test with "Jest" or "Jest test", but no test match if run with "Jest test/components" Is there any workaround for this? We need to have different setupFiles/testEnvionment for different subfolder. Not sure how to achieve this with this bug. |
As @lippea mentioned, we encountered this problem. It doesn't seem to be limited to Windows Server 2012; more Windows machines in general. Mac machines are okay. We worked around this for the time-being by using a separate |
I was having the same problem on Windows 7 enterprise. I can confirm that the problem was related to having either a space or bracket in the path. Once I removed those the tests would run. |
@mikehdt can you provide your example? I'd prefer your solution over my current one. |
@mikehdt How do you use that |
I'm still dealing with the same issue as @josalmi . |
If you are all running into this issue, please send a PR to fix it for everyone. We don't have Windows 7 machines, so unless you guys send a PR, this won't get fixed :) Thank you. |
Confirming problem, not clever enough to solve it. @mikehdt More on that json workaround would be appreciated. |
A workaround for anyone having this problem with jenkins is to set a custom workspace directory for your project under the project's advanced settings. Just set it to a path without spaces (e.g. c:\workspace\my-project). |
I think this is the same problem as #2381. Closing in favor of the other issue. Still looking for help on 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. |
No tests found: when running Jest under Windows Server 2012 environment.
The issue is only reproducible when the project path contains space.
My jest configuration is:
node: v6.9.1
npm: 3.10.8
Jest: 18.1.0
The text was updated successfully, but these errors were encountered: