Dmitry Dygalo
Dmitry Dygalo
The main problem with state-machine-based stateful testing is that in some cases, it is too verbose. E.g., if the test is flaky, then Hypothesis will output a very long traceback,...
**Is your feature request related to a problem? Please describe.** When I test my SaaS implementation I use a copy-pasted version of Schemathesis' test app which I need to keep...
Now examples are tested separately, but it seems like it should be beneficial to use examples in tests that use only generated data (it is also concluded in section 5.3.3...
**Is your feature request related to a problem? Please describe.** It might be beneficial to change the ordering of unit tests in some cases. For example, if there are two...
**Describe the bug** If the tested schema consists of multiple files, then Schemathesis will inline components only from the root schema, which is insufficient if parameter schemas contain references to...
Now, all components are copied to intermediate schemas passed to `hypothesis-jsonschema` so all references can be resolved. The problem is that if the schema is huge, it might be problematic...
**Is your feature request related to a problem? Please describe.** Currently, Schemathesis reports only the first found JSON Schema error. It can report all found JSON schema errors. **Describe the...
TODO. extend description
The current CLI is focused on unit tests, but I think that state-machine-based stateful tests do not fit this output style. For this reason, the CLI output can be separated...
This piece is definitely missing. Inspired by https://matklad.github.io//2021/02/06/ARCHITECTURE.md.html