coverage-report
Here are 237 public repositories matching this topic...
-
Updated
Mar 31, 2022 - JavaScript
-
Updated
Apr 5, 2022 - Ruby
-
Updated
Apr 11, 2022 - Rust
-
Updated
Oct 11, 2021 - Groovy
-
Updated
Mar 28, 2022 - Ruby
-
Updated
Mar 31, 2022 - PHP
It seems hard to go into a JavaScript/TypeScript library's issues and not have someone asking about Deno
Well, here it is: does typescript-coverage-report support Deno?
-
Updated
Feb 21, 2022 - Python
-
Updated
Aug 28, 2020 - JavaScript
-
Updated
Jan 13, 2022 - Ruby
-
Updated
Jul 31, 2020 - Ruby
-
Updated
Apr 7, 2022 - Scala
-
Updated
Apr 2, 2022 - Go
-
Updated
Dec 6, 2021 - Python
-
Updated
Oct 8, 2018 - Ruby
-
Updated
Apr 4, 2020 - C++
-
Updated
Sep 16, 2021 - JavaScript
-
Updated
Jan 30, 2022 - Python
-
Updated
Nov 30, 2020 - PHP
-
Updated
Dec 9, 2021
-
Updated
Feb 12, 2020 - PHP
-
Updated
Aug 12, 2020 - Haskell
-
Updated
Dec 13, 2021 - Python
-
Updated
Apr 6, 2022 - Python
If I understand it correctly, right now this package isn't compatible with Windows because there's no windows version of LCOV. And trying to run the genhtml Perl script runs into errors because of Windows paths.
Locally, I've gotten around this by installing LCOV in WSL. Then, it's two lines of code:
First, I replace the slashes in lcov.info:
``run(`bash -c "tr '\\' '/' < coverage/lcov.i
Improve this page
Add a description, image, and links to the coverage-report topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the coverage-report topic, visit your repo's landing page and select "manage topics."
We have a problem: if files aren't loaded/required we don't have branch data. If they are added through
track_fileswe give it 0/0 branches which we show as 100% coverage (all possible branches are covered).That math is "wrong" though here because there are branches but we don't know what they are. We should probably count total branches here as "unkown" and establish that in our "math unive