-
As a coverage tool, it is highly unlikely that a library will include a genuine dependency on `org.jacoco.*`. However;
- There are no safeguards in place. If this does happen, `bazel coverage` may …
-
Currently, we use CodeCov to report `Golang` test coverage in our repository, but we're missing coverage information for the web scope. As a first step, we aim to add the `web/crux` scope to the cover…
-
similar to echidna: https://github.com/crytic/echidna/releases/tag/v2.0.4
-
Document how to read backend coverage reports, specifically where "overall line coverage" is shown. See https://github.com/oppia/oppia/pull/17788#issuecomment-1503784737. Also suggest `python -m cover…
-
### What was wrong?
```
$ curl -L https://coveralls.io/coveralls-linux.tar.gz | tar -xz -C .
$ ./coveralls --help
bash: ./coveralls: cannot execute binary file: Exec format error
```
I think thi…
-
## Problem Description
When running tests in parallel across multiple workers, our project sends several coverage files to Codecov. The current behavior of Codecov triggers an email notification upon…
-
Current status
I don't think there is a significant difference between html-spa and html reports
Expectation
html-spa can be referenced as a react component that can combine coverage json data wi…
-
**Is your feature request related to a problem? Please describe.**
Ideally functional tests should strive for full coverage, with the exception being impossible paths based on the inability to force …
-
Hi, this has been very useful. I do have on issue that if others are seeing, would be nice to have addressed: I get a coverage report such as:
coverage/ | 82.15 | 58.46 | 80…
-
I had 255 test cases and 77 cases failed
I had these errors, is it because of that?
```
Error: The 'summary' will be truncated because the character limit (65535) exceeded.
Error: The 'text' wil…