-
It was discussed in https://github.com/systemd/systemd/pull/33146#issuecomment-2146720903 but looking at https://github.com/systemd/systemd/pull/33524 I think it would be nice if mkosi provided a way …
-
### Describe the feature
We would like to have code coverage reports for all our `zenoh-*` repos.
https://blog.rng0.io/how-to-do-code-coverage-in-rust/ has a good initial example of how to do it f…
-
### 🚀 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…
-
We need to implement a mechanism in Vitest to generate coverage reports for each story file. This task focuses on collecting coverage data for all affected files when a story file is executed, and out…
-
https://github.com/jpb06/coverage-badges-action/issues/5#issuecomment-2129494828
> What we could do is also generating an average set of badges for all apps/libs. For example, if I have two apps wi…
jpb06 updated
2 weeks ago
-
I'm attempting to comprehend why the project, which I aim to enhance, yields quite [inconsistent coverage results](https://introspector.oss-fuzz.com/project-profile?project=quickjs). Upon examining th…
-
We currently cover a lot of code via anvil integration tests, but those are not added to the code coverage reports.
I think it's nice to add the anvil coverage to the reports so that we know what p…
-
To provide comprehensive coverage information, we need to ensure that the coverage reports in the Storybook UI display coverage data for all relevant files associated with a component. This includes n…
-
# Implementation
1. Exclude from reports:
- generated files
- "API files", e.g. https://github.com/status-im/status-go/pull/5237
2. Create a Notion page for issues
3. Make the check req…
-
[@dnephin commented in @302](https://github.com/gotestyourself/gotestsum/issues/302#issuecomment-1513993027) in a discussion about coverage output:
> go tool cover (https://pkg.go.dev/cmd/cover) is a…