3 ms·
> What are the benefits of building out a whole separate part of the test framework that handles this? Instead of making it part of the base runner? Maybe so t
by masklinn 5y ago
> What are the benefits of building out a whole separate part of the test framework that handles this?
Instead of making it part of the base runner? Maybe so the beta bits can work and it’ll be folded in more directly afterwards?
Also if it includes coverage guiding being able to know that a run is fuzzing or non-fuzzing would avoid having to include the fuzzing instrumentation for non-fuzzing run, mayhaps?
> Is there a way to fuzz non-string inputs?
From the design doc it looks like you can have any number of parameters and
> Fuzzing of built-in types (e.g. simple types, maps, arrays) and types which implement the BinaryMarshaler and TextMarshaler interfaces are supported.
- kubb 5y agoI was thinking a library to generate fuzzed inputs that you could use in normal tests. It's good to hear that it's not limited to strings.
- masklinn 5y ago> I was thinking a library to generate fuzzed inputs that you could use in normal tests. The fuzzer input is random data. You don't need a special library to generate random data. In fact that's what the post tells you with respect to type compatibility: > types which implement the BinaryMarshaler and TextMarshaler interfaces are supported these are just tools to convert from/to binary (unstructured or utf8).
- kubb 5y agoAre you sure it's random bytes? Some fuzzers start with a given input and then mutate it to increase coverage of the code under test.
- masklinn 5y ago> Some fuzzers start with a given input and then mutate it to increase coverage of the code under test. Yes, and this one does, but you requested a library to generate inputs didn't you? A library can't get coverage feedback from the SUT, which as I wrote in my previous comment would be why you'd be building a dedicated test framework.