Does Portman provides automatic fuzzing for "happy" test paths.

[PaulCluver]

Hi there,

The fuzzing for the "unhappy" test paths works beautifully. Is there an option to "fuzz" for happy test paths. In other words, automatically removing object or key:value pairs from the generated request that are NOT required?

Kind regards,
Paul

BTW: Portman has truly revolutionalized how I do API testing. It is a fantastic tool.

[thim81]

@PaulCluver

I'll have to review the code, but I think the Fuzzy testing is mostly focused on finding "unhappy" situations.
Could you explain to me why you would want to remove non-required properties?

[PaulCluver]

Thanks for getting back to me. My idea was sparked by the following from documentation at https://github.com/apideck-libraries/portman/tree/main/examples/testsuite-fuzzing-tests

Instead of me having to configure all happy path variations, I was hoping that these could simply be generated. I am dealing with a very large request body so tracking down all possible 2xx variations which need to be exercised is somewhat laborious.

Another example is with a variation test that I have written. This test removes a non-required portion of the request body using the below:

Submitting this request, as the removed property is not required, should result in a 2xx response. Instead, I get a 400 - Bad Request. While I have captured this as an issue, I am concerned that there may be many more. This is why I was hoping to be able to generate all possible permutations of a request where I remove non-required properties.

I hope that this provides some context.

Kind regards,
Paul.

[thim81]

@PaulCluver

I think it would be possible to develop the happy path option for removing "non-required" properties. It has been a while so we would need some time to dive in again.

[PaulCluver]

Hi Tim,

Thanks so much for considering this as a an option.

Kind regards,
Paul.

[thim81]

hi @PaulCluver

Apologies, but we haven't found the time to look into this.