> I am approaching it like learning a new unit-test framework. That's reasonable. If you just take a step back from afl or libfuzzer and consider how you wou

> I am approaching it like learning a new unit-test framework. That's reasonable. If you just take a step back from afl or libfuzzer and consider how you would test your product with arbitrary inputs, the critical steps that you have to take are pretty similar regardless of the framework. It has to be noninteractive and it should ideally be something whose duration doesn't vary by many orders of magnitude (so you can set sane timeouts that you consider failures). It shouldn't have any nondeterminism or behaviors that consider other inputs outside of the ones generated by the fuzzing framework. It's great if you can avoid filesystem interaction.