-
Any two files with identical names will make `Danger`/`Shroud` output bogus numbers for the coverage percentage.
It's not too strange on a large project (perhaps with many modules) to have a couple…
-
### Describe the bug
We have a multimodule project with module structure:
- root (org.acme.testcoverage)
- common (org.acme.testcoverage.common)
- service (org.acme.testcoverage.service)
…
-
Seems like related to https://github.com/jacoco/jacoco/pull/288. Need to investigate
-
With catch-exception, I get code coverage on the test code completely. With this library, I lose that. I assume this is because the code under test that throws the exception is not wrapped as it is …
-
Hello @GaelGirodon,
First of all, let me say that I'm quite happy to have found you GitHub Actions, as it is exactly what I wanted!
But I have an issue about JaCoCo code coverage reporting.
Con…
-
Hi,
I am trying to determine the code coverage but I am amazed to find that Jacoco plugin reports zero unit test coverage although a sizeable amount of unit tests exist.
Am I missing something he…
-
We have been trying to compile our jacoco test report, while the team has three different coverage statistics and even one of us get a significantly lower branch coverage. Is that ok if we use the sam…
-
### Describe the bug
Most of our repos are structured as multi-module repos. Some modules are quarkus-services, some are only libs which are shared between the quarkus-services. Every module had the …
-
Add more unit tests to improve code coverage to each class in Token Service
1. Checked box without issue indicates False negative for coverage where codacy reports 0% coverage but test exists.
2. …
-
I setup this file in GitHub to report the coverage to codacy:
https://github.com/LibrePDF/OpenPDF/blob/master/.github/workflows/maven.yml
the relevant part is this:
```
codacy-coverage-reporter…