-
Notifications
You must be signed in to change notification settings - Fork 54
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
[WIP] #261: Add fuzz test #270
Conversation
First time working with Looking for pointers to improve and extend this PR - specifically (but not limited to):
Any feedback is appreciated. |
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.
Regarding mage, I'd recommend adding a separate command for fuzzing, and making sure you include the flag -fuzztime
. A sensible default can be 10 seconds.
After you add the mage command, we can include it as part of the CI pipeline. Let me know if that all makes sense and thanks!
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.
Thanks for doing this! One small comment but looks great.
Ohhh I forgot - it would make sense to include this in the github CI. Take a look at the |
Overview
WIP PR for issue#261
Description
Adds:
How Has This Been Tested?
With commands:
mage fuzz
mage test