Schemathesis

:version:`1.3.0 <v1.2.0...v1.3.0>` - 2020-04-27
-----------------------------------------------

**Added**

- Storing network logs with ``--store-network-log=<filename.yaml>``.
The stored cassettes are based on the `VCR format <https://relishapp.com/vcr/vcr/v/5-1-0/docs/cassettes/cassette-format>`_
and contain extra information from the Schemathesis internals. :issue:`379`
- Replaying of cassettes stored in VCR format. :issue:`519`
- Targeted property-based testing in CLI and runner. It only supports the ``response_time`` target at the moment. :issue:`104`
- Export CLI test results to JUnit.xml with ``--junit-xml=<filename.xml>``. :issue:`427`

**Fixed**

- Code samples for schemas where ``body`` is defined as ``{"type": "string"}``. :issue:`521`
- Showing error causes on internal ``jsonschema`` errors during input schema validation. :issue:`513`
- Recursion error in ``response_schema_conformance`` check. Because of this change, ``Endpoint.definition`` contains a definition where references are not resolved. In this way, it makes it possible to avoid recursion errors in ``jsonschema`` validation. :issue:`468`

**Changed**

- Added indentation & section name to the ``SUMMARY`` CLI block.
- Use C-extension for YAML loading when it is possible. It can cause more than 10x speedup on schema parsing.
Do not show Click's "Aborted!" message when an error occurs during CLI schema loading.
- Add a help message to the CLI output when an internal exception happens. :issue:`529`

:version:`1.2.0 <v1.1.2...v1.2.0>` - 2020-04-15
-----------------------------------------------

**Added**

- Per-test hooks for modification of data generation strategies. :issue:`492`
- Support for ``x-example`` vendor extension in Open API 2.0. :issue:`504`
- Sanity validation for the input schema & loader in ``runner.prepare``. :issue:`499`

:version:`1.1.2 <v1.1.1...v1.1.2>` - 2020-04-14
-----------------------------------------------

**Fixed**

- Support for custom loaders in ``runner``. Now all built-in loaders are supported as an argument to ``runner.prepare``. :issue:`496`
- ``from_wsgi`` loader accepts custom keyword arguments that will be passed to ``client.get`` when accessing the schema. :issue:`497`

:version:`1.1.1 <v1.1.0...v1.1.1>` - 2020-04-12
-----------------------------------------------

**Fixed**

- Mistakenly applied Open API -> JSON Schema Draft 7 conversion. It should be Draft 4. :issue:`489`
- Using wrong validator in ``response_schema_conformance`` check. It should be Draft 4 validator. :issue:`468`

:version:`1.1.0 <v1.0.5...v1.1.0>` - 2020-04-08
-----------------------------------------------

**Fixed**

- Response schema check for recursive schemas. :issue:`468`

**Changed**

- App loading in ``runner``. Now it accepts application as an importable string, rather than an instance. It is done to make it possible to execute a runner in a subprocess. Otherwise, apps can't be easily serialized and transferred into another process.
- Runner events structure. All data in events is static from now. There are no references to ``BaseSchema``, ``Endpoint`` or similar objects that may calculate data dynamically. This is done to make events serializable and not tied to Python object, which decouples any ``runner`` consumer from implementation details. It will help make ``runner`` usable in more cases (e.g., web application) since events can be serialized to JSON and used in any environment.
Another related change is that Python exceptions are not propagated anymore - they are replaced with the ``InternalError`` event that should be handled accordingly.

:version:`1.0.5 <v1.0.4...v1.0.5>` - 2020-04-03
-----------------------------------------------

**Fixed**

- Open API 3. Handling of endpoints that contain ``multipart/form-data`` media types.
Previously only file upload endpoints were working correctly. :issue:`473`