-
The approach described [here](https://jbp.io/2017/07/19/measuring-test-coverage-of-rust-programs) uses llvm profile compiler runtime library, which has several benefits.
Most interestingly, it seems …
-
## Description
HI! I am using my fuzz testing tool to test this library, and so far I have found 15 different bugs. Among them, there are 5 array out-of-bounds errors, 3 string encoding errors, 1 unw…
-
### What problem does your feature solve?
Fuzz testing currently requires compiling contracts to native code. Wasm code is a black box to the fuzzer and it gets no feedback from it.
For the …
brson updated
6 months ago
-
It would be nice if we were able to gather test coverage information for Clippy.
We have [an old script][script] written by @mcarton that could be used to run `kcov` on Clippy. It seems like this s…
-
First, thanks for a very useful tool!
It would be nice if there was an command line option to merge the coverage of different instantiations of generic functions in the summary of the coverge of a …
-
### Discussed in https://github.com/sourcefrog/cargo-mutants/discussions/23
Originally posted by **xd009642** February 13, 2022
So this may be worth creating an issue for, but this is largely …
-
Hello, I've got a question whether it's possible or maybe there exists a dedicated mechanic to building the instrumented binary and generating reports separately.
The use case would be integration …
-
Since at least `nightly-2023-12-04` compiling `wlcs_anvil` from [`smithay`](https://github.com/smithay/smithay) using `RUSTFLAGS="-Cinstrument-coverage"` results in an internal compiler error.
Firs…
-
### Problem
I was looking at a performance issue caused by env RUSTFLAGS="-Cinstrument-coverage" in our codebase and have determined that the major part of the degradation (~10x slowdown) was because…
-
i have a simple module with tests for each of the functions/methods written, but the report says a percentage are missing -- not sure why -- how can i determine what is considered missing?