-
-
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
coverage.raw.json? #2861
Comments
I don't know. Do you want to find out and send a PR if it doesn't? |
Can you point to how jest uses istanbul? I'll compare the configuration settings I normally use to what jest does. |
cc @DmitriiAbramov wrote all of the coverage support, he may be able to help you out. |
hey @ljharb! |
Pretty outdated so closing (also phrased as a question opposed to a feature request). @ljharb please open a new feature request if this is still something we dont have that you want us to add! |
It’s definitely something i still want; i can open a new issue if necessary or can retitle instead. |
Yeah, if you wouldn't mind filling out the issue template, that'd be awesome. |
istanbul produces a
coverage.raw.json
file, which is useful for regenerating different reports after the fact, or merging coverage reports from multiple runs (say, the same tests but on multiple node versions, where different feature checking branches apply). I use https://www.npmjs.com/package/istanbul-merge to merge those raw coverage files into a single report.Can jest produce
coverage.raw.json
just like istanbul?The text was updated successfully, but these errors were encountered: