Dmitry Dygalo

By coincidence, the very same behavior happened to me yesterday - I was canonicalising the [Swagger schema](https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v2.0/schema.json) (where `$schema` points to draft04) components and my test suite started failing when...

With the `example` based implementation, it can't work - `example` is constructed by Schemathesis and expects exact values. But if `test_api` uses `data` to draw values interactively, then the user...

`TypeError` related to the usage of numeric HTTP codes should be resolved by #1294

Hi @basbossink-ds Good catch! Let me fix it :)

That issue is going to be fixed in #1564. I'll release a new version during this week

Yeah, a similar issue was also mentioned in [this comment](https://github.com/schemathesis/schemathesis/issues/1147#issuecomment-979980389) in #1147. > It would be handy to pass a (comma-separated?) list of forbidden HTTP status codes to schemathesis run...

@ivanych Пардон, дам развернутый ответ в течении пары дней. Но в кратце - да, я бы хотел видеть такую фичу в Schemathesis в перспективе

В данный момент чтобы провалидировать схему можно использовать такой Python сниппет: ```python from schemathesis.specs.openapi.definitions import OPENAPI_30_VALIDATOR, SWAGGER_20_VALIDATOR # For Open API 3 OPENAPI_30_VALIDATOR.validate({...}) # For Open API 2 SWAGGER_20_VALIDATOR.validate({...}) ```...

> Попробовал CLI из jsonschema. Сообщения у них, конечно, не очень-то говорящие — в большинстве случаев is not valid under any of the given schemas и гадай — что именно...

Hi @dwreeves ! Indeed, gathering filtering logic like this makes sense to me :) However, I am mostly concerned about the high-level API. At the moment, I am inclined to...