-
- [ ] for functional tests
- [ ] for unit tests
-
So, one thing our company likes to see is code coverage numbers. I'd love to see this plugin enable support for this.
Mainly, I'd like to see two things:
* Code coverage indicators by the line nu…
-
Looking through some of the CVID cases and seeing some odd results with coverage. For the variant shown below, the tool tip states the coverage as 9, 12 and 6 for the three sample, but the coverage tr…
-
Test coverage is being reported as:
```
Statements : 100% ( 79/79 ), 3 ignored
Branches : 96.15% ( 75/78 ), 12 ignored
Functions : 100% ( 20/20 ), 1 ignored
Lines : 100% ( 38/38…
-
I'm using Infrabox to show the coverage report of my unit tests and it's great, but it'd be even greater if the there was an improvement in the UI. Currently it's a little difficult to do any analysis…
-
As asked in https://github.com/codecov/codecov-action/issues/1487#issuecomment-2258551527, I'm opening a new ticket.
The failure is still happening for tokenless uploads for `doctrine/dbal`. What's w…
-
**Bug report**
I was reviewing the pyarrow PR and noticed that the usual codecov summary was missing. Looking at the `Unit Tests and Coverage` workflow, I see this error under the `upload coverage r…
-
Looks like code coverage from sonarcloud is not being reported. It does seem to be calculated on sonarcloud. Investigate why it's not showing up. Looks like it does calculate it for pull requests.
…
-
bazel coverage with the following additional build setting leads to .dat files not getting generated
```
build --@rules_rust//rust/settings:experimental_use_cc_common_link=true
```
To repro,…
-
There should be a build producing coverage reports and reporting whether the coverage was increased or lowered by the changes.