Bump schemathesis from 3.1.0 to 3.6.1 in /api

[dependabot]

Bumps schemathesis from 3.1.0 to 3.6.1.

Release notes

Sourced from schemathesis's releases.

v3.6.1

🐛 Bug fixes

• f8d90b9 Using parametrized pytest fixtures with the from_pytest_fixture loader

🔧 Chores and Improvements

• 24212a9 Release 3.6.1
• 3b10a2b (deps) Bump Sphinx version

📦 Other

• 9afd280 Fix example for APIStateMachine.get_call_kwargs

v3.6.0

🚀 Features

• 9ac1b75 More GraphQL loaders
• 36c0c87 Support for data_generation_methods and code_sample_style in all GraphQL loaders
• 22354a9 ASGI support for GraphQL schemas
• 0bf11c7 Support for app & base_url arguments for the from_pytest_fixture runner
• fa0820f from_wsgi loader for GraphQL apps

🐛 Bug fixes

• d558063 Return type of make_case for GraphQL schemas
• dbd6720 Silently ignoring some incorrect usages of @​schema.given`
• 90198ec Missing @schema.given implementation for schemas created via the from_pytest_fixture loader

🔧 Chores and Improvements

• 60ed847 Release 3.6.0
• 301dfae Fix tox warning
• 1f69add Deprecate schemathesis.runner.prepare
• 04f22e8 Initial support for GraphQL schemas in Schemathesis runner
• a2d9beb Loaders unification
• 7586416 Improve error handling on from_path incorrect usage
• ced53fc Validate schema paths in ASGI / WSGI loaders
• 08ba562 Validate GraphQL loaders in Schemathesis runner
• a25b91c Fix invalid import
• 70754a5 Add blank impl for GraphQLSchema.get_stateful_tests
• 5307af4 Unify test IDs
• 3355ce9 Use different DB entries for each API operation in CLI
• d689d77 Update GraphQL loader
• e69a2ea Do not show overly verbose raw schemas in Hypothesis output for failed GraphQL tests
• c46d5b8 Generate separate tests for each field for GraphQL schemas

... (truncated)

Changelog

Sourced from schemathesis's changelog.

3.6.1_ - 2021-04-09

Fixed

• Using parametrized pytest fixtures with the from_pytest_fixture loader. [#1121](https://github.com/schemathesis/schemathesis/issues/1121)_

3.6.0_ - 2021-04-04

Added

• Custom keyword arguments to schemathesis.graphql.from_url that are proxied to requests.post.
• from_wsgi, from_asgi, from_path and from_file loaders for GraphQL apps. [#1097](https://github.com/schemathesis/schemathesis/issues/1097), [#1100](https://github.com/schemathesis/schemathesis/issues/1100)
• Support for data_generation_methods and code_sample_style in all GraphQL loaders.
• Support for app & base_url arguments for the from_pytest_fixture runner.
• Initial support for GraphQL schemas in the Schemathesis runner.

.. code-block:: python

import schemathesis
Load schema
schema = schemathesis.graphql.from_url("http://localhost:8000/graphql")
Initialize runner
runner = schemathesis.runner.from_schema(schema)
Emit events
for event in runner.execute():
...

Breaking

• Loaders' signatures are unified. Most of the arguments became keyword-only. All except the first two for ASGI/WSGI, all except the first one for the others. It forces loader calls to be more consistent.

.. code-block:: python

# BEFORE
schema = schemathesis.from_uri(
    "http://example.com/openapi.json", "http://127.0.0.1:8000/", "GET"
)
# NOW
schema = schemathesis.from_uri(
    "http://example.com/openapi.json", base_url="http://127.0.0.1:8000/", method="GET"
)

Changed

• Schemathesis generates separate tests for each field defined in the GraphQL Query type. It makes the testing process unified for both Open API and GraphQL schemas.

... (truncated)

Commits

• 24212a9 chore: Release 3.6.1
• f8d90b9 fix: Using parametrized pytest fixtures with the from_pytest_fixture loader
• 9afd280 docs: Fix example for APIStateMachine.get_call_kwargs
• 3b10a2b chore(deps): Bump Sphinx version
• 60ed847 chore: Release 3.6.0
• 9ac1b75 feat: More GraphQL loaders
• 301dfae chore: Fix tox warning
• 1f69add chore: Deprecate schemathesis.runner.prepare
• 04f22e8 chore: Initial support for GraphQL schemas in Schemathesis runner
• 0f50b02 refactor(runner): Move fixups installation out of Schemathesis runner
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)