Dmitry Dygalo

> Is that not what the fuzzer originally does? By default, Schemathesis generates data that matches the API schema. Except for some cases like integer formats that are not supported...

Hi @hoog1511 Thanks for reporting! I am leaning towards the first option with an error message. The latter one feels like it will hide the fact that one of the...

Hi @tl-madhulika-mitra Thanks for opening the issue, that is indeed a bad error report from Schemathesis. As far as I see, the underlying issue is that some of the security...

Thanks for more context! Can it be that you have `$ref` inside one of your security scheme definitions? Not inside the `securitySchemes` key, but inside individual items there?

> a few $ref are under securitySchemes but most of them are not. So you think this caused the error? Most likely so, because the `type` key is required there....

Additionally/alternatively it would be nice to investigate pairwise testing for the current implementation. Similar to https://github.com/pairwise-testing/python-allpairspy Maybe not as a default way of testing, but via e.g. a config parameter

Thank you for opening the issue and the provided details! There are a few things I'd like to mention as an explanation for this behavior, but indeed it is confusing...

Sure! I suggest following steps from our [contributing guide](https://github.com/schemathesis/schemathesis/blob/master/CONTRIBUTING.rst#submitting-pull-requests) :) Once you set up a local copy with pre-commit enabled, you can implement points from the task description. Let me...

Hi @vkosuri It is something that I plan to add to Schemathesis.io first (at least 6+ months from now), as the feature is quite large. Let me know if you...

> In order to conformance on asyncapi it requires some checks, curious to know how to put a check because it uses publish/subscribe where publisher fire and ignore and where...