You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to test some wildly incorrect graphql input and ensure the parser, and the compiler, and any other tools that might use these two crates are error resilient and don't panic. It would be good to figure out a succinct way to either run apollo-smith in a completely chaotic graphql environment, or to have some sort of separate fuzzing.
~ chaos ~ engineering ~
The text was updated successfully, but these errors were encountered:
We want to be able to test some wildly incorrect graphql input and ensure the parser, and the compiler, and any other tools that might use these two crates are error resilient and don't panic. It would be good to figure out a succinct way to either run
apollo-smith
in a completely chaotic graphql environment, or to have some sort of separate fuzzing.~ chaos ~ engineering ~
The text was updated successfully, but these errors were encountered: