Skip to content
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 report incorrectly generated with v1.1.0 #266

Open
NTaylor1993 opened this issue Mar 14, 2022 · 1 comment
Open

Coverage report incorrectly generated with v1.1.0 #266

NTaylor1993 opened this issue Mar 14, 2022 · 1 comment

Comments

@NTaylor1993
Copy link
Contributor

Description

After upgrading to v1.1.0 coverage reports are no longer generating correctly. Previously coverage for the full repo would be in the report however now it only shows some files under the report eg:

-----------------------------------------------|---------|----------|---------|---------|--------------------------------------------------------------------------------

File % Stmts % Branch % Funcs % Lines Uncovered Line #s
All files 87.45 75.67 82.88 87.63
events.js 71.64 46.15 69.23 71.9
----------------------------------------------- --------- ---------- --------- --------- --------------------------------------------------------------------------------

It does not always seem to return the same files, in the report. The example above comes from a worst case scenario I have seen but sometimes a few extra files do show up.

This seems to be related to the change to Jest v27 and the testRunner that is set by default. In Jest v27 the runner is set by default to jest-circus/runner whereas before it was set to jest-jasmine2

Changing the jest.config.js to specify testRunner: jest-jasmine2 seems to fix the issue it would be great if this could either be fixed in the repo or specified by default.

@joeythomaschaske
Copy link

I have a similar issue where no coverage is being reported on 1.2.1. I need to explicitly set coverageProvider in my jest.config.js file for it to show

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants