Skip to content
This repository has been archived by the owner on Oct 9, 2019. It is now read-only.

Please contribute examples of fuzzing and shrinking bugs #190

Open
mgold opened this issue Jul 7, 2017 · 0 comments
Open

Please contribute examples of fuzzing and shrinking bugs #190

mgold opened this issue Jul 7, 2017 · 0 comments

Comments

@mgold
Copy link
Member

mgold commented Jul 7, 2017

It seems that the implementation of fuzzers and especially shrinkers is constantly in flux. But, we also appear to be designing blind.

I am asking for real-world examples of when 100-run fuzz tests were unsatisfactory. That is, SSCCEs of code and test where the tests either do not detect a bug or shrink to an unhelpfully large counterexample. Also indicate the (human-derived) smallest failing value that the fuzzer did not find.

Again, real-world examples: something that came up in production Elm code or caused you a significant amount of troublesome debugging.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant