No option to ignore path(s) when collecting test coverage

[timothytong]

Currently the only option to not generate coverage for certain files or directories is to use the --collectCoverageOnlyFrom option in our package.json files. However, I ran into a problem when I wanted to test all js files in my codebase but just a couple files that are already being tested somewhere else (please don't ask why there are reasons behind that). IMHO, enumerating all those files would

1. be a pain in the butt
2. result in a gigantic package.json file
3. just not make sense at all..
   In conclusion, I wish there was a --collectCoverageIgnorePaths option for developers.

[cpojer]

I agree! Would you mind sending a pull request for this? This should be in the config and not part of the CLI and should be fairly straightforward to implement. I'd call it coverageIgnorePaths.

[bookman25]

It'd be nice if it used minimatch as well and not regex.

[cpojer]

This unfortunately has to use regex to stay consistent with the rest of Jest.

Changing Jest to other matching algorithms is part of our plan to rewrite configs, but shouldn't be done in this change :)

[cpojer]

This is going to be in #1233 and will be tagged soon! :)

[github-actions]

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.