-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fuzz tests #137
Add fuzz tests #137
Conversation
Co-authored-by: Samuel Laferriere <[email protected]>
@anupsv why did we never merge this? Do you want to rebase so we can merge? Hopefully its not too gnarly |
That's a good question. Idk why we didn't merge it. I'll rebase and merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Haven't actually read through the tests but let's just merge and if they are flaky we can deal with them later. Better to have more protection than less.
Things to look for in the future:
- don't think we need the
FUZZ=true
env var, go fuzzer (https://pkg.go.dev/testing) seems to only run fuzz testing when you add the -fuzz - 15m seems a bit long if our other tests run in <10 mins. We might want to bring this down.
Fixes Issue
Fixes #
Changes proposed
Screenshots (Optional)
Note to reviewers