-
Our current test coverage is still lacking in several areas and we certainly encountered breakage around edge cases that were not properly covered with tests even though the happy path had tests.
T…
-
When using `-Zinstrument-coverage` on a recent (first-week-of-May-2021) nightly, the `matches!` macro is no longer marked covered. (This is likely related to macro coverage rules recently adjusted…
-
The Rust unstable book includes some examples of the workflow for generating LLVM coverage reports using [`-Z instrument-coverage`](https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/instr…
-
-
kevgo updated
2 years ago
-
I am striving for a high test coverage in `nucleo`. The matcher crate and the pattern parsing should already hit 80% test coverage. I would like to track coverage automatically in CI (for example wit…
-
I don't want to write a separate test framework for the C code in the project. Cargo-llvm-cov can generate code coverage for C, and I'm glad it has this feature.
However, now I have encountered a …
-
From `cargo llvm-cov --workspace`
```
Filename Regions Missed Regions Cover Functions Missed Functions Executed Lines Missed Lines Cover Branches …
-
I’m trying to set up sccache and I have a wrapper script at a location `scripts/coverage-wrappers/rustc` that I set `RUSTC_WORKSPACE_WRAPPER` to.
Cargo then invokes `$RUSTC_WRAPPER $RUSTC_WORKSPACE…
-
Take a look at https://github.com/taiki-e/cargo-llvm-cov, hopefully will be less manual than what we're doing now!
Also look at https://github.com/taiki-e/coverage-helper, and see if we can run tests…