-
Integrate code coverage tools to track the percentage of code covered by tests.
Acceptance Criteria: Code coverage reports are generated after each test run, with results accessible to the team.
-
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…
-
When I pass all the XML files (jacocoreport.xml) from the multi module project, I see that there is a discrepancy in the coverage report. I submit the code coverage to sonarQube the coverage is around…
-
The current setup of the **apiclient-boilerplate-dotnet** repository includes code coverage reporting to the following platforms:
- **SonarCloud**: Receives all coverage reports (unit and integration…
-
The following issues are all tied-together with the ideas of identifying documents and sections and what they contain, and then checking if it made it into OMOP or not.
- #81 is about a new table t…
-
**Artifact Under Review**
3.6.3 Success Criteria
**Team Number for Team Doing the Review**
27
**Description of Issue**
One extra additional criteria that I can think of is code coverage and u…
-
### Describe the bug
When running vitest with --coverage using Storybook Test plugin, the reports include story files, which is not expected and affects coverage calculations:
![Image](https://githu…
-
### 🚀 Feature Proposal
An easy way to run Jest but generate coverage separately for each test file.
### Motivation
A common pattern is to have a test file for each source file. But coverage is gene…
-
Consider adding test coverage score on README.md using badge. See [`genbadge`](https://smarie.github.io/python-genbadge/), Github Actions ([1](https://github.com/marketplace/actions/coverage-badge), […
-
Enable `codecov` as other projects in open-telemetry did. This requires maintainer status.
References:
- see https://github.com/open-telemetry/community/issues/1926
- see https://docs.codecov.com…