-
-
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
Coverage hasn't worked since last major semver update #1425
Comments
hey @dsifford all make a fix for it on monday! |
@DmitriiAbramov Wow, that's great to hear! Thanks so much again for your work on this! |
I'm getting the same issue. Looking forward to the fix! |
@DmitriiAbramov Thanks again for the quick fix with this. Does Jest have pre-release or nightly branches that I can pull with these changes? If not, any idea when the next update will be pushed through? |
we're going to release the next version in about two weeks or so. |
I'm more or less continuously pushing a I published @DmitriiAbramov's fix a minute ago, so please feel free to try it out. It's |
Awesome, sounds good. Thanks again so much! |
Not sure if you guys are aware, but the issue is persisting with Still no coverage being rendered. Happy to answer any specific questions either of you may have. |
@dsifford the bug was actually in jest tried it on |
also now you can add something like this to your jest config "jest": {
"collectCoverageFrom": ["src/**/*.{js,ts,tsx}", "!**/{vendor,__tests__}/**"]
} and this will also collect coverage for all files that are not tested but match this set of globs |
@DmitriiAbramov Ah, ok sorry about the confusion. Thanks for the clarification. Got it working now. Also: |
I tried using collectCoverageFrom, after putting that in the config,I received:
|
@calclavia is there any stack trace? does it happen after/before or during the test run? |
It happens during the test run. I'll try to come up with a stack trace soon. |
I have the same issue. I use a custom preprocessor (because jest fails when using CSS modules). When removing that custom preprocessor, then it seems to pick up the code without a problem. Could it be related to that? My preprocessor is pretty much this one: Stacktrace:
|
that should be fixed by #1482 |
Thanks. I'll try to test it today. I ended up throwing the preprocessor away in favour of another method. :) |
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. |
Hello,
I've been trying to troubleshoot this on my own off and on for the last few days, but unfortunately I haven't been able to figure out what's going on. Issue #433 seems to be the closest thing to what I have going on, but none of the suggestions there helped.
Before the last major semver update, everything was working totally fine. Now, when I run jest with the same configs as before I get this.
For some reason, no tests are making it to the results table and, although coverage report is being generated, it's completely blank.
Here's my configs:
It looks like a week or so ago
collectCoverageFrom
has been added to master, but that hasn't been released yet, so that's not really an option for now.Here's the repo: https://github.com/dsifford/academic-bloggers-toolkit
Happy to answer any questions you might have. Thanks in advance for your work on this!
The text was updated successfully, but these errors were encountered: