-
Hi,
When checking coverage report via Web UI, I see stale data. However, when checking coverage command-line, i.e.
go test -v -coverprofile cover.out
with
go tool cover -html=cover.out -o coverage.ht…
-
In larger programs and real-world projects it's often difficult to know whether a certain part of code was actually analyzed or not.
Dead code warnings provide only partial information because the la…
-
Currently if one test is failing the whole pipeline stops and no coverage reports can be created.
In my opinion if a test is failing it should still be possible to generate coverage for the non-faili…
-
**Is your feature or enhancement request related to a problem or limitation? Please describe**
We used to have coverage reports for the CICS CLI plug-in
**Describe your enhancement idea*…
-
At the time this issue was created, there are several uses of `paramError` in `AdvancedExtrudedGenerator` that the test suite does not hit, as shown by coverage reports. These parameters are:
* dir…
-
This is related to #532. This should:
1. Move from coverage to `pytest-cov` for better feature support.
2. Restrict coverage reports to unit testing based suites, and excluding integration testing…
-
I am experiencing a problem with multiple projects and multiple build frameworks (C# .NET code). My project structure is as follows ([link](https://github.com/marthijn/Sidio.OpenGraph)):
- /src/a/
-…
-
Business Reason
As a user, I will be alerted to verify coverage dates since the dates cannot be changed once the report is created, so that my created Form 3x reports will have the correct coverage d…
-
We have started integrating with codecov to improve the unit test coverage. This will provide the unit test code coverage and make sure the unit test coverage is improved over time.
However, there…
-
Recently, I implemented the [tokio runtime](https://tokio.rs/) for asynchronous execution of
- REST API calls (the pure python project doesn't implement this)
- running clang-tidy and/or clang-forma…