-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
collectCoverage do nothing when using projects configs #8722
Comments
Yeah, That probably should be a project one (and setting the flag from the CLI would just set it to We'll be revisiting config and its validation as part of Jest 25 where we'll either fix this somehow or at the very least provide good error messages if fields are added where they don't belong (#7185 is a tracking issue for this work) |
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. |
🐛 Bug Report
collectCoverage do nothing when using projects configs.
global jest.config.js
client jest.config.js
To Reproduce
Code above. Jest run through CLI with command like
npm test -- someTests
I was trying to debug the jest and in places where jest uses
collectCoverage
option it trying to access it fromglobalConfig
that pointed to rootjest.config.js
When i moved all coverage options from project config to root config - coverage working.
Expected behavior
collectCoverage
option should work.Link to repl or repo (highly encouraged)
No link, sorry.
Run
npx envinfo --preset jest
Paste the results here:
The text was updated successfully, but these errors were encountered: