-
-
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 is only collected from javascript files #9490
Comments
Can confirm, jest 25.1 stopped to collect coverage from vue files. 24.9 is fine. |
Same here. Downgrading to Jest 24 fixes the issue and
|
I'm facing the same issue, but if I try to downgrade to 24 my tests fails
The solution posted here works fine for me: |
Had to downgrade jest to v24. Coverage is broken for non-js files in v2: jestjs/jest#9490
The update to Jest 25.2.4 (possibly earlier already) seems to have fixed the issue. With nextcloud/tasks@5dd7179 I see the coverage being reported for vue files again. |
Seems to have fixed the coverage issue. Ref: jestjs/jest#9490 (comment)
I close this since the issue is fixed with 25.2.4.. |
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. |
💥 Regression Report
Coverage data is only collected from javascript files, but not from e.g. vue files, although configured to collect data from vue files as well.
Last working version
Worked up to version: 24.9.0
Stopped working in version: 25.1.0
To Reproduce
Steps to reproduce the behavior:
Have a repository with js and vue files and configure jest to report coverage for both file types using this configuration:
Run jest and see that coverage is only reported for js files. The problem might be related to #9464.
Expected behavior
Coverage should be reported for js and vue files.
Link to repl or repo (highly encouraged)
The repository is https://github.com/nextcloud/tasks. If a minimal example is preferred I can provide one as well.
Run
npx envinfo --preset jest
The text was updated successfully, but these errors were encountered: