-
Notifications
You must be signed in to change notification settings - Fork 107
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
Generated HTML has errors for some files (0% coverage even though showing non-zero items) #279
Comments
Is there a any solution for this? @jhpedemonte @inacior @bahmutov same problem here, i tried to remove
****************************************************** |
is there any solution to this ? |
Hi @VendenIX . This issue is very old and, unfortunately, the original reproduction case is no longer valid. If you have a complete reproduction of this issue against the latest version of Cypress and this plugin we'd be happy to investigate - please open a new issue with all requested template items filled out and we'll take a look. |
Logs and screenshots
Versions
"@cypress/code-coverage": "^3.8.1"
"cypress": "4.10.0"
RHEL
sh
12.14.1
(Using Docker imagecypress-included:4.10.0
🤷
Use
craco
to customizecreate-react-app
's webpack config to add thebabel-plugin-instanbul
plugin. Similar to what is done byinstrument-cra
but building instead of running in dev mode (similar to cypress-io/instrument-cra#135 (comment)).window.__coverage__
object? Can you paste a screenshot?.nyc_output
folder? Is there.nyc_output/out.json
file. Is it empty? Can you paste at least part of it so we can see the keys and file paths?package.json
(nyc
object) or in other NYC config filesYes, custom image based on
cypress-included:4.10.0
.Describe the bug
After building an instrumented build and running Cypress tests, the generated HTML code coverage report shows some files with 0% coverage but actually having some non-zero covered code (see screenshots above).
When viewing one such file in the HTML report, it will show an error instead of file contents:
The text was updated successfully, but these errors were encountered: