Re:I've fuzzed parts of the GitHub API. Here are my findings
by aszen on Friday December 02, 2022 @04:52PM
(#33837438)
Say i have an order record, it needs company and product.
The fuzzer should be smart enough to first generate company and product then use them to create orders. Similarly the fuzzer should be able to build a whole graph of the api data model and be able to execute actions on it in a particular order testing all the actions
Currently, there is some support for resource correlation. Especially when fuzzing DELETE, it will identify a successful POST based on conventions and use that as an identifier. Also checking that DELETEd resources are not available anymore.