Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Running coverage locally shows empty coverage report
See original GitHub issueAs tested on 9b986ab79a00d9a0119985142362f45e4eb8e27c on the main branch, in a clean repository, ran the following commands:
npm install
npm run build
npm run coverage
The terminal log showed that all the tests ran and that that coverage task completed in 2 minutes, however, the report opened up as empty:
This does not seem to be a problem in CI.
Issue Analytics
- State:
- Created a year ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Command line usage — Coverage.py 6.4.4 documentation
When you install coverage.py, a command-line script called coverage is placed on ... By default, each run of your program starts with an...
Read more >Coverage in HTML view is broken · Issue #9388 · facebook/jest
Run the script with npm test -- --coverage; When opening the coverage/lcov-report/index.html the HTML does not show the coverage report ...
Read more >Troubleshooting Code Coverage - Visual Studio (Windows)
Learn how to resolve erroneous empty results messages when you expect Visual Studio to collect data for native and managed assemblies.
Read more >Jest finds tests but doesn't collect coverage - Stack Overflow
I found that when upgrading jest (from 23 to 26) that i had this issue, and the resolution was to run with the...
Read more >Code coverage reports - AWS CodeBuild
To create a code coverage report, you run a build project that is configured with at least one code coverage report group in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@sanjeetsuhag I think you mean
(\\|\/)instead to escape the forward slash?The cause of this issue is the regex filter for the instrumented plugin not working for the Windows path separator:
https://github.com/CesiumGS/cesium/blob/0fcd8ca4d0d64f0d9b10c04608f938337f629c2a/gulpfile.js#L1148
I believe all the
\\should be(\\|\/)instead.