-
Code coverage is collected by [collect_coverage.rs](https://github.com/bazelbuild/rules_rust/blob/main/util/collect_coverage/collect_coverage.rs). This binary invokes `llvm_profdata` and `llvm_cov`, w…
-
Here are the main areas which need improvement:
- [x] `SignedXml.CheckSignature(X509Certificate2 certificate, bool verifySignatureOnly)` - currently no coverage - sample code should be sufficient for…
-
-
Is it possible to generate coverage without `deno test` but with `deno run`? This would enable generating coverages for custom test runners.
-
### What is the problem this feature will solve?
This issue is for tracking remaining work to stabilize code coverage in the test runner. When this feature originally shipped, it had documented lim…
-
In composer.json there is a definition of command `test-coverage`, which doesn't seem to be used anymore and perhaps could be deleted.
`.travis.yml` has a logic to fire this command depending on `$TE…
rarog updated
2 months ago
-
### New issue checklist
- [X] I searched for [existing GitHub issues](https://github.com/microsoft/azure-pipelines-tasks/issues)
- [X] I read [pipeline troubleshooting guide](https://docs.microsoft.c…
-
### Description
The unit test coverage of all the packages in Vitess need to be checked and improved upon.
We can look at https://app.codecov.io/gh/vitessio/vitess/tree/main for better guidance on…
-
Include unit tests for predicates discussed in README.
Target coverage %: 80+ for core (predicate eval, standardizing block)
-
It would be nice if somehow we could badge the README in our repo automatically with the coverage results.