-
My repo contains 3 Python projects in a "projects" dir, and I'm running `pytest --cov=packageA projects/packageA/tests` (for each of the 3 projects). The 2nd project in the test sequence (so the 2nd `…
-
Some workflows, like the _tests_, will trigger on a merge and then again on the release tag. It seems wasteful and unnecessary if the workflow already passed on the merge prior to tag/release.
- …
-
The goal of this workstream is to increase confidence in each component, not just to increase coverage. It’s better to have 80% coverage with high-quality tests than 100% coverage with low-quality tes…
-
Hi @rillig
First of all Thanks so much for Branch(C1) and Condition(C2) coverage implementation. It helps us a lot.
I have to find C1 for whole project. So I planned to pass packages one by one…
-
Current state -
- Cypress UI tests for input errors
- Unit Tests and branch coverage report
-
In my code structure, there are multiple directories under `src`, and there is one directory `test` which contains unit test files.
My `mocha_istanbul` configuration as follows:
```
mocha_istanbu…
-
### What happened?
When running tests under `bazel coverage` (or `bazel test --collect_coverage`), Node running via `js_test` is being instrumented regardless of the [--instrument_test_targets](htt…
-
We have a default configuration specified in our .nycrc with the following:
```
{
"extends": "@istanbuljs/nyc-config-typescript",
"reporter": ["text", "html", "lcov"],
"check-coverage…
-
Running munit with -coverage, I get an empty coverage report:
```
------------------------------
COVERAGE REPORT
------------------------------
OVERALL COVERAGE STATS:
packages 0% 0 …
-
## Problem statement
As a fairly big feature to introduce into tarpaulin I'm creating an issue to track things that need to be investigated/implemented/solved to achieve decision (a.k.a branch) cov…