-
# **Feature Request:** istanbuljs / nyc test coverage report validation along with individual files with different configuration 🙏🏼
This is not an issue, needs some confirmation about nyc configura…
-
I am using grcov 0.8.19 on Windows Server 2022 x86_64. When I run the following command from Git Bash, I get a panic:
```
grcov . --binary-path target/debug/deps/ \
-s . \
-t covdir \
…
-
My use case:
1. `dev` branch is the main
2. feature branches are merged into `dev`
3. a pull-request from `dev` into `staging`, then `staging` into `prod` is done to produce releasable versions
4.…
-
**Is your feature request related to a problem?**
Insufficient code coverage for unit tests.
**What solution would you like?**
Write unit test cases and cover the uncovered code.
**Do you have…
-
We have a goal to reach 70% of code coverage in the kubewarden controller repository. For that, we can improve the coverage of the `internal` package. The first package that must need to be improved i…
jvanz updated
3 months ago
-
To get coverage run `npm run test:coverage`. The result will look something like this:
```
=============================== Coverage summary ===============================
Statements : 94.51% ( 86/…
-
Hi there,
In the instrumenter code while walking on an if statement node and building the branch map I've noticed that the else statement locations is always the same as the if statement locations.
W…
-
# Summary
When using pytest --cov together with a FastAPI app, sqlalchemy (async Postgres connection) and pytest-docker (for the DB) we get back wrongly calculated coverage for the services. For orga…
-
As of f89eb89, coverage output looks like this:
```
--------------------|----------|----------|----------|----------|----------------|
File | % Stmts | % Branch | % Funcs | % Li…
-
Please integrate my branch at http://code.google.com/r/arveknudsen-cover-parallel. The goal of this branch is to make the coverage plugin able to support coverage's parallel mode.
The motivating scen…