-
-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage broken when using babel-jest #304
Comments
@jehoshua02 I encountered this issue too when using |
Same issue here, is there a workaround?
|
Any ideas how to solve this issue that I can try? |
Im running into this also, so close to working! |
The problem is in the istanbul package in report/html.js, there appears to be an some sort of error where the report is expecting another line and there is none. I changed the function to
and got
I think it is some kind of mapping error by babel, telling istanbul there is one more line then there should be? Not really sure though. Hopefully this can help someone with a little experience with these libraries. |
Is there any progress on this? |
I updated the versions and it seems to be working now. You can see how I am using it here https://github.com/ericwooley/react-in-style |
I'm still seeing this problem, on node v0.10.38 |
Same here |
I'm experiencing this issue with Node v4.0.0 and Jest v |
Working for me on |
Not working for me on |
I'd like to fix this if it is still causing trouble for people. Can someone provide me a proper repro against jest 0.8 or 0.9? |
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. |
The issue can reproduced by following these precise steps:
And I get this output:
As you can see, the tests run fine, and pass, the coverage is output to the console (which is all I really want), but something after that, I'm assuming when writing out reports to the disk, is failing and generating a big ugly error.
Issue also reported over at babel-jest.
The text was updated successfully, but these errors were encountered: