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
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:
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.
The text was updated successfully, but these errors were encountered:
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
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:
-----------------------------------------------|---------|----------|---------|---------|--------------------------------------------------------------------------------
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 tojest-circus/runner
whereas before it was set tojest-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.The text was updated successfully, but these errors were encountered: