-
Notifications
You must be signed in to change notification settings - Fork 426
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
Fuzz testing with cargo fuzz #642
Comments
I set up a basic It got up to 1.8M executions (~20 minutes) and then segfaulted:
Apparently there is a known bug in At any rate, it seems like what's really getting exercised is @LegNeato is that as intended? Also, I'm not sure if the async-flavored |
Ok, here's the AFL version: trevyn/juniper@master...trevyn:fuzz-afl Ran it for 30 minutes with no issues, will leave it running and report back later. |
1 crash found: crash-0000.min I added a (failing) test to the trevyn:fuzz-afl branch. |
In addition to the stack overflow crash above, it's also easy to hit a |
Woah, totally missed this, great work! Is it ready to be integrated? |
@trevyn , FWIW I was thinking about this due to 17d474e. I wonder if there is a way to give a schema and have a bunch of valid and invalid permutations thrown at us. Would be useful for all GraphQL servers to have a corpus of graphql queries with corresponding schema and if they should pass / not pass. |
@LegNeato Thanks! I’m not working with Juniper or GraphQL anymore, but feel free to use anything here! |
We should fuzz test
execute
andexecute_async
to make sure no external input can cause the library to panic or crash.The text was updated successfully, but these errors were encountered: