Examples
| Item | Description |
|---|---|
| Full Fuzzer Name | ExamplesFieldsFuzzer |
| Log Key | EF |
| Description | This fuzzer will send full request examples as defined in the OpenAPI specs. The expectation is that APIs will treat these requests as happy path. The fuzzer aims to check that all examples defined in the OpenAPI specs are correct and in-line with the request schemas. |
| Enabled by default? | Yes |
| Target field types | N/A |
| Expected result when fuzzed field is required | 2XX |
| Expected result when fuzzed field is optional | 2XX |
| Expected result when fuzzed value is not matching field pattern | 2XX |
| Fuzzing logic | Iteratively sends unique request examples defined at the media-type, schema, or property level in the OpenAPI specs. |
| Conditions when this fuzzer will be skipped | When the request does NOT have any example or examples defined at the requestBody, schema, or property level |
| HTTP methods that will be skipped | HEAD, TRACE, DELETE |
| Reporting | Reports error if: 1. response code is 404; 2. response code is documented, but not expected; 3. any unexpected exception. Reports warn if: 1. response code is expected and documented, but not matches response schema; 2. response code is expected, but not documented; 3. response code is 501. Reports success if: 1. response code is expected, documented and matches response schema. |