-
Updated
Nov 4, 2020 - TypeScript
coverage
Here are 894 public repositories matching this topic...
-
Updated
Jul 15, 2020 - JavaScript
-
Updated
Jan 28, 2021 - Java
It would be helpful if the lcov generated reports could generate relative paths. My use case is that I am generating coverage reports from a docker image and then using VS Code Coverage Gutters which supports relative paths to view the coverage. But it doesn't work because the absolute paths on the docker c
-
Updated
Feb 2, 2021 - Ruby
-
Updated
Jan 21, 2021 - CMake
-
Updated
Sep 1, 2020 - JavaScript
-
Updated
Jan 26, 2021 - PHP
-
Updated
Jan 29, 2021 - C#
-
Updated
Dec 31, 2017 - PHP
-
Updated
Jan 25, 2021 - Java
-
Updated
Dec 18, 2020 - JavaScript
-
Updated
Jan 29, 2021 - Rust
-
Updated
Jan 30, 2021 - Perl
-
Updated
Jan 26, 2021 - Groovy
-
Updated
Feb 2, 2021 - Ruby
-
Updated
Jan 1, 2021 - C++
-
Updated
Nov 30, 2020 - Ruby
-
Updated
Aug 11, 2020 - Shell
Is your feature request related to a problem? Please describe.
We have a database schema which includes temporary objects - this means objects which are required only for a short time like procedure for upgrades or objects which are still work in progress - and legacy test code. Temporary objects are always prefixed with the username of the author like:
windowsusr_my_table
Test Procedures a
As for our project , we need more detail coverage data about every js file, so can you add the following info to classElement.
classElement.setAttribute("lines-covered", "" + file.getCodeLinesCoveredCount());
classElement.setAttribute("lines-valid", "" + file.getCodeLineCount());
classElement.setAttribute("branchs-covered", "" + file.getBranchesCoveredC
-
Updated
Nov 20, 2020 - Nim
Since dotnetcore's behavior when testing entire solution is trying also test non testing projects and then whole process is evaluated as non successful at least on linux, then I need to run test on one by one testing project separately I need to somehow then merge altcover results into one xml file, is that possible?
-
Updated
Nov 10, 2020 - JavaScript
-
Updated
Jan 17, 2021 - Kotlin
Improve this page
Add a description, image, and links to the coverage topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the coverage 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