-
```
If you call gcov with "gcov -b -c", it provides enough information that you
can measure both branch and condition coverage. It would be really nice if
CoverStory handled them also.
(If you do wor…
-
Sometimes I want to gather coverage for multiple packages in a mono_repo.
I tried to be smart, and run things in parallel, but that doesn't work:
```
$ (cd ../native_assets_cli/ && dart pub glo…
-
Unit-tests are already running as part of CICD.
Need to add coverage report
-
While our Windows Security pipeline provides coverage for a broad range of Event ID's, we still have significant gaps in our coverage. Windows Event IDs have around 85% coverage of Windows Specific te…
-
It would be nice if somehow we could badge the README in our repo automatically with the coverage results.
-
This issue is a progress tracker on the potential to improve the test coverage in RosettaSciIO:
**Formats missing test files**:
- [ ] netCDF
**Formats with coverage below 80%**:
- [ ] digital-…
-
Test coverage has languished a bit recently, and we want to make sure that we not only have good coverage, but that we understand the coverage that we have.
-
**Is your feature request related to a problem? Please describe.**
When users polish long read assemblies with short reads, they tend to believe that the new consensus is always better than the origi…
-
Make github action to run tests and test coverage, generate a badge and put it in the README.
-
Coverage, test, lint etc have different output formats, adding flags for each isn't scalable.
We should collapse these into a single enum selector, something along the lines of `--format=` for 2.0.
…