Automated fuzz testing of OpenAPI definitions
Problem to solve
Users can spend a lot of time making crisp API definitions in the OpenAPI format. Requiring them to re-define the endpoints and settings for fuzzing means it takes them more, resulting in either frustration or simply not doing it due to the time required.
Intended users
Further details
Proposal
When an OpenAPI definition file is detected in the repository, automatically create and run fuzz tests as part of a pipeline.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Sam Kerr