You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 from globalConfig that pointed to root jest.config.js
When i moved all coverage options from project config to root config - coverage working.
That probably should be a project one (and setting the flag from the CLI would just set it to true for every project).
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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
🐛 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: