auto-fuzz-test icon indicating copy to clipboard operation
auto-fuzz-test copied to clipboard

Effortlessly fuzz libraries with large API surfaces

Results 9 auto-fuzz-test issues
Sort by recently updated
recently updated
newest added

* [x] `Vec` * [ ] tuples like `(T, V)` * [ ] `HashMap` * [ ] slices etc.

tracking-issue

Our unit tests works as follows: 1. Copy 'tests/test-lib' to target 2. Build 'target/test-lib' (this invokes our macro and creates 'target/test-lib/fuzz' directory with different fuzz-targets) 3. Build each fuzz-target in...

enhancement

Hello 👋 I am the maintainer of [fuzzcheck](https://github.com/loiclec/fuzzcheck-rs), which is a fuzzing engine built for Rust. For now, fuzzcheck works in the same way as cargo-fuzz in that one needs...

enhancement

Today's implementation is able to handle only bare types (such as `MyType`) or references to bare types (`&MyType` and `&mut MyType`). I want to implement a function, which will recursively...

enhancement

By now explanation in [README.md](https://github.com/rust-fuzz/auto-fuzz-test/blob/master/README.md) looks very vague, but I can't think of anything better.

enhancement

More info here: https://github.com/rust-fuzz/cargo-fuzz/issues/174 This looks like an upstream bug - not even in cargo-fuzz but in libfuzzer. We need to figure out a minimal example and report it to...

Fuzzing harness generator should operate in a manner similar to `cargo fuzz init`: it should create a subfolder in your project that would already have a Cargo.toml and have everything...

This project could use a catchier name. The goal is to make it possible to fuzz libraries with large API surfaces. This is currently impractical because fuzzing harnesses have to...

Functions with lifetimes in signatures are not currently handled correctly. The input is parsed, but the generated output does not compile.