Great to see fuzzing becoming more mainstream. Ultimately we have absurd program states, with even a trivial program's state vastly exceeding the number of particles in the universe. We need to start finding order-of-magnitude-better approaches for testing.
I almost always write generated tests at this point with unit tests being a fallback for slow code or niche cases. What I dont generally write though is fuzz tests, which would really be a 'next step'. In Rust it's not very hard to do so, but it hasn't quite hit the "trivial" mark yet for me, whereas quickcheck is virtually the same amount of work to use as to not use.
Languages like Go adopting and mainstreaming these practices will be a benefit to everyone.
I'm curious if there's documentation on:
a) The coverage approach taken
b) The mutation approach taken
Can you configure these? Plugin different fuzzing backends?
I almost always write generated tests at this point with unit tests being a fallback for slow code or niche cases. What I dont generally write though is fuzz tests, which would really be a 'next step'. In Rust it's not very hard to do so, but it hasn't quite hit the "trivial" mark yet for me, whereas quickcheck is virtually the same amount of work to use as to not use.
Languages like Go adopting and mainstreaming these practices will be a benefit to everyone.
I'm curious if there's documentation on:
a) The coverage approach taken
b) The mutation approach taken
Can you configure these? Plugin different fuzzing backends?