Léo Gaspard

Tag release-blocking issues

3

Hey! From my experience with it I'm thinking Marvin is really great already, and could probably already be released on some percentage of all incoming github PRs (just changing the...

Document the testing process

1

Hey! In the same idea as https://github.com/timokau/marvin-mk2/issues/112 ; would it be possible for you to write some documentation for how you test marvin when you develop on it? Creating multiple...

Marvin for issues

1

Hey! This is again an idea that can safely be postponed to after marvin with its current feature set lands. I'm thinking, something similar to marvin would probably make sense...

Improving on the rate-limiting algorithm

1

Based on the comments on https://github.com/timokau/marvin-mk2/pull/101, it sounds like currently marvin's rate-limiting algorithm is based on “involves the person and was updated in the last N days”. This attempts to...

allow bolero tests to run on wasm32-unknown-unknown

2

This PR allows crate developers to run `bolero::check!()` tests on wasm32-unknown-unknown. This is not fuzzing yet, but at least basic proptesting works there, with this PR :) Considering the infrastructure...

Construct fuzzer input from known result (AntiGenerator?)

10

This may be a far-fetched idea, but I'm just dropping it here in case it'd make sense: what would you think about the idea of making an "anti-generator" function in...

`cargo bolero repro` command?

2

I can't find a way to repro a single fuzzer crash from the `cargo bolero` command line. Am I missing something, or should we add such a way, eg. `cargo...

Detangling Driver and DriverMode

2

So, continuing the discussion started on https://github.com/camshaft/bolero/pull/108#discussion_r1083565909 ; let's chat about driver and driver mode here. I guess my first question would be, is there any user-facing use case for...

Switching to a magic number-based collection generator?

7

Hey! I've just recently had a look at the TypeGenerator for Vec, and noticed that the collection generators seem to use a tag-length-value format. Such a format is very quickcheck-friendly...

Stats: marking known-useless runs

2

Assume a fuzzer that looks like: ```rust #[test] fn fuzzer() { check!().for_each(|i: &[u8]| { if let Ok(i) = parse_input(i) { the_thing_we_actually_want_to_fuzz(i) } }) } ``` Basically, any run that does...