schemathesis 3.29.2__tar.gz → 3.30.0__tar.gz

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/build.yml

@@ -26,7 +26,7 @@ jobs:
     name: Generic pre-commit checks
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
 
@@ -41,7 +41,7 @@ jobs:
     name: Documentation
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
       - uses: ammaraskar/sphinx-action@master
@@ -58,15 +58,12 @@ jobs:
           - os: ubuntu-22.04
             python: "3.9.16"
             tox_env: pytest6
-          - os: ubuntu-22.04
-            python: "3.9.16"
-            tox_env: pytest53
       fail-fast: false
 
     name: Tests (Python ${{ matrix.python }} on ${{ matrix.os }} ${{ matrix.tox_env }})
     runs-on: ${{ matrix.os }}
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
 
@@ -83,6 +80,6 @@ jobs:
         run: python -m tox
 
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v4.4.1
+        uses: codecov/codecov-action@v4.5.0
         with:
           token: ${{ secrets.CODECOV_TOKEN }}

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/codeql-analysis.yml

@@ -30,7 +30,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4.1.6
+        uses: actions/checkout@v4.1.7
         with:
           # We must fetch at least the immediate parents so that if this is
           # a pull request then we can checkout the head.
@@ -38,7 +38,7 @@ jobs:
 
       # Initializes the CodeQL tools for scanning.
       - name: Initialize CodeQL
-        uses: github/codeql-action/init@v3.25.6
+        uses: github/codeql-action/init@v3.25.10
         with:
           languages: ${{ matrix.language }}
           # If you wish to specify custom queries, you can do so here or in a config file.
@@ -49,7 +49,7 @@ jobs:
       # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
       # If this step fails, then you should remove it and run the build manually (see below)
       - name: Autobuild
-        uses: github/codeql-action/autobuild@v3.25.6
+        uses: github/codeql-action/autobuild@v3.25.10
 
       # ℹ️ Command-line programs to run using the OS shell.
       # 📚 https://git.io/JvXDl
@@ -63,4 +63,4 @@ jobs:
       #   make release
 
       - name: Perform CodeQL Analysis
-        uses: github/codeql-action/analyze@v3.25.6
+        uses: github/codeql-action/analyze@v3.25.10

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/codspeed.yml

@@ -11,7 +11,7 @@ jobs:
   benchmarks:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
       - uses: actions/setup-python@v5
         with:
           # Python 3.12 for flamegraph support

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/commit.yml

@@ -12,7 +12,7 @@ jobs:
     runs-on: ubuntu-22.04
     steps:
       - name: Check out code
-        uses: actions/checkout@v4.1.6
+        uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 0
       - name: Run commitsar

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/example-build.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
 
       - name: Start containers
         run: docker compose up -d --build

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/master_update.yml

@@ -20,7 +20,7 @@ jobs:
             tag: "latest-bookworm"
 
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
 
       - name: Set up QEMU
         uses: docker/setup-qemu-action@v3

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
             tag-suffix: "-bookworm"
 
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
 
       - name: Docker meta
         id: meta
@@ -68,7 +68,7 @@ jobs:
     name: Build and publish package to pypi.org
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/test-corpus.yml

@@ -15,7 +15,7 @@ jobs:
     name: Corpus tests
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/test-hypothesis.yml

@@ -11,7 +11,7 @@ jobs:
     name: Hypothesis tests with CI profile
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/update-corpus.yml

@@ -10,7 +10,7 @@ jobs:
     name: Update test corpus
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.29.2 → schemathesis-3.30.0}/.github/workflows/update-pre-commit.yml

@@ -10,7 +10,7 @@ jobs:
     name: Update pre-commit
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.6
+      - uses: actions/checkout@v4.1.7
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.29.2 → schemathesis-3.30.0}/.pre-commit-config.yaml

@@ -38,12 +38,12 @@ repos:
         additional_dependencies: [types-click, types-requests, types-PyYAML]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.4.5
+    rev: v0.4.10
     hooks:
       - id: ruff-format
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.4.5
+    rev: v0.4.10
     hooks:
       - id: ruff
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: schemathesis
-Version: 3.29.2
+Version: 3.30.0
 Summary: Property-based testing framework for Open API and GraphQL based apps
 Project-URL: Documentation, https://schemathesis.readthedocs.io/en/stable/
 Project-URL: Changelog, https://schemathesis.readthedocs.io/en/stable/changelog.html

{schemathesis-3.29.2 → schemathesis-3.30.0}/benches/cli.py

@@ -1,4 +1,5 @@
 import sys
+
 import pytest
 
 pytest_plugins = ["pytester"]

{schemathesis-3.29.2 → schemathesis-3.30.0}/benches/schema.py

@@ -12,7 +12,7 @@ CURRENT_DIR = pathlib.Path(__file__).parent.absolute()
 sys.path.append(str(CURRENT_DIR.parent))
 CATALOG_DIR = CURRENT_DIR / "data"
 
-from corpus.tools import read_corpus_file, load_from_corpus  # noqa: E402
+from corpus.tools import load_from_corpus, read_corpus_file  # noqa: E402
 
 CORPUS_OPENAPI_30 = read_corpus_file("openapi-3.0")
 CORPUS_SWAGGER_20 = read_corpus_file("swagger-2.0")

{schemathesis-3.29.2 → schemathesis-3.30.0}/changelog.py

@@ -1,6 +1,7 @@
 """Simple CLI for changelog management."""
 
 from __future__ import annotations
+
 import argparse
 import datetime
 import re

{schemathesis-3.29.2 → schemathesis-3.30.0}/docs/changelog.rst

@@ -1,9 +1,71 @@
 Changelog
 =========
 
-:version:`Unreleased <v3.29.2...HEAD>` - TBD
+:version:`Unreleased <v3.30.0...HEAD>` - TBD
 --------------------------------------------
 
+.. _v3.30.0:
+
+:version:`3.30.0 <v3.29.2...v3.30.0>` - 2024-06-23
+--------------------------------------------------
+
+**Added**
+
+- **EXPERIMENTAL**: New stateful test runner in CLI. :issue:`864`
+- The ``--experimental=stateful-only`` CLI flag to run only stateful tests if the new test runner is enabled. Note that this feature is experimental and may change in future releases without notice.
+- Ability to extract values from headers, path, and query parameters using regular expressions in OpenAPI links.
+- The ``negative_data_rejection`` check. It ensures that the API rejects negative data as specified in the schema.
+- The ``use_after_free`` check. It ensures that the API returns a 404 response after a successful DELETE operation on an object. At the moment, it is only available in state-machine-based stateful testing.
+- Support for building dynamic payloads via OpenAPI links. This allows for building objects or arrays where nested items are not hardcoded but dynamically evaluated.
+- ``APIStateMachine.format_rules`` method to format transition rules in a human-readable format.
+
+.. code-block::
+
+    POST /user
+    └── 201
+        ├── GET /users/{ids}
+        └── DELETE /user/{id}
+
+    GET /users/{ids}
+    └── 200
+        └── PATCH /user
+
+    DELETE /user/{id}
+    └── 204
+        └── DELETE /user/{id}
+
+**Changed**
+
+- Enforce the ``minLength`` keyword on string path parameters to avoid the rejection of empty values later on.
+  This improves the performance of data generation.
+- Rework building state machines for stateful testing to improve performance.
+- Improve error messages on ``MaxRetryError``. :issue:`2234`
+- Migrate to new-style ``pytest`` hooks. :issue:`2181`
+- Filter out Hypothesis' warning about resetting the recursion limit in multi-worker tests.
+- Show sub-schema location in ``response_schema_conformance`` failure messages. :issue:`2270`
+- Avoid collecting data for stateful tests in CLI when they are explicitly disabled.
+
+**Fixed**
+
+- Internal error during OpenAPI link resolution if the needed parameter is missing in the response.
+- Improper output when a JSON pointer can't be resolved during OpenAPI link resolution.
+- Generating invalid examples created by wrapping a named example value into another object. :issue:`2238`
+- Distinguish more failures in stateful testing.
+- Generate different functions for state machine transitions to properly use swarm testing.
+- ``RuntimeError`` caused by a race condition when initializing Hypothesis' PRNG in multiple workers.
+- Missing body in ``Case`` if it is mutated after the ``make_case`` call. :issue:`2208`
+- Internal error when a rate limiter hits its limit. :issue:`2254`
+- Internal error during reference resolving when using relative file paths.
+- Ignoring property examples defined under the ``example`` key in Open API 2.0 schemas. :issue:`2277`
+
+**Removed**
+
+- Support for ``pytest<6.0``.
+
+**Performance**
+
+- Improve performance of copying schemas.
+
 .. _v3.29.2:
 
 :version:`3.29.2 <v3.29.1...v3.29.2>` - 2024-05-31

{schemathesis-3.29.2 → schemathesis-3.30.0}/docs/cli.rst

@@ -123,6 +123,7 @@ There are four built-in checks you can use via the `--checks / -c` CLI option:
 - ``status_code_conformance``. The response status is not defined in the API schema;
 - ``content_type_conformance``. The response content type is not defined in the API schema;
 - ``response_schema_conformance``. The response content does not conform to the schema defined for this specific response;
+- ``negative_data_rejection``. The API accepts data that is invalid according to the schema;
 - ``response_headers_conformance``. The response headers does not contain all defined headers.
 
 To make Schemathesis perform all built-in checks use ``--checks all`` CLI option:

{schemathesis-3.29.2 → schemathesis-3.30.0}/docs/experimental.rst

@@ -112,6 +112,35 @@ To enable OpenAPI 3.1 support via environment variables, you can set:
 
 For more details, join the `GitHub Discussion #1822 <https://github.com/schemathesis/schemathesis/discussions/1822>`_.
 
+.. _stateful-test-runner:
+
+New Stateful Test Runner
+~~~~~~~~~~~~~~~~~~~~~~~~
+
+This experimental feature enables a more effective way to run stateful tests in the CLI, along with a new display style. 
+It leverages state machines, which were previously available in the ``pytest`` integration, to generate more diverse test scenarios. 
+By default, state machines are executed until no new failures are found in a single iteration.
+
+.. important::
+
+   The new test runner does not yet support all configuration options available in the old one.
+
+In CLI
+~~~~~~
+
+.. code-block:: bash
+
+    st run https://example.schemathesis.io/openapi.json --experimental=stateful-test-runner
+
+Using Environment Variables
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. code-block:: bash
+
+    export SCHEMATHESIS_EXPERIMENTAL_STATEFUL_TEST_RUNNER=true
+
+For more details, join the `GitHub Discussion #2262 <https://github.com/schemathesis/schemathesis/discussions/2262>`_.
+
 Schema Analysis
 ~~~~~~~~~~~~~~~
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/docs/python.rst

@@ -102,7 +102,7 @@ For example, to override a query parameter and path:
 
 
     @schema.parametrize()
-    @schema.override(path_parameters={"user_id": "42"}, query={"apiKey": "secret"}}
+    @schema.override(path_parameters={"user_id": "42"}, query={"apiKey": "secret"})
     def test_api(case):
 
 This decorator overrides the ``apiKey`` query parameter and ``user_id`` path parameter, using ``secret`` and ``42`` as their respective values in all applicable test cases.
@@ -298,7 +298,9 @@ When the received response is validated, Schemathesis runs the following checks:
 - ``status_code_conformance``. The response status is not defined in the API schema;
 - ``content_type_conformance``. The response content type is not defined in the API schema;
 - ``response_schema_conformance``. The response content does not conform to the schema defined for this specific response;
+- ``negative_data_rejection``. The API accepts data that is invalid according to the schema;
 - ``response_headers_conformance``. The response headers does not contain all defined headers.
+- ``use_after_free``. The API returned a non-404 response a successful DELETE operation on a resource. **NOTE**: At the moment it is only available in state-machine-based stateful testing.
 
 Validation happens in the ``case.call_and_validate`` function, but you can add your code to verify the response conformance as you do in regular Python tests.
 By default, all available checks will be applied, but you can customize it by passing a tuple of checks explicitly:

{schemathesis-3.29.2 → schemathesis-3.30.0}/docs/stateful.rst

@@ -485,10 +485,62 @@ Each additional test will be indented and prefixed with ``->`` in the CLI output
 You can specify recursive links if you want. The default recursion depth limit is **5** and can be changed with the
 ``--stateful-recursion-limit=<N>`` CLI option.
 
-Schemathesis's CLI currently uses the old approach to stateful testing, not based on state machines.
-We plan to use the new approach in CLI in the future. It may include slight changes to the visual
-appearance and the way to configure it. It also means that using stateful testing in CLI is not yet as customizable
-as in the in-code approach.
+Schemathesis's CLI now supports the new approach to stateful testing based on state machines. 
+It is available as an experimental feature and can be enabled using the ``--experimental=stateful-test-runner`` CLI option or by setting the
+``SCHEMATHESIS_EXPERIMENTAL_STATEFUL_TEST_RUNNER=true`` environment variable. For more information, refer to the :ref:`stateful-test-runner` section.
+
+.. code-block::
+
+    Links                                                  2xx    4xx    5xx    Total
+
+    POST /api/users/
+    └── 201
+        ├── GET /api/users/{user_id}                       765      0    101      866
+        └── PATCH /api/users/{user_id}                     765      0      0      765
+
+    GET /api/users/{user_id}
+    └── 200
+        └── PATCH /api/users/{user_id}                     513      0      0      513
+
+
+The old approach to stateful testing, not based on state machines, is still the default in the CLI. 
+However, we recommend using the new approach as it offers more effective testing. 
+In the future, the new approach will become the default in the CLI, and the old approach will be removed.
+
+Please note that the visual appearance and configuration options for stateful testing in the CLI may differ slightly from the in-code approach. 
+We are continuously working on improving the CLI experience and aligning it with the in-code approach.
+
+Extracting data from headers and query parameters
+-------------------------------------------------
+
+By default, Schemathesis allows you to extract data from the response body of an API endpoint, based on the provided schema. 
+However, sometimes you might need to extract data from other parts of the API response, such as headers, path or query parameters.
+
+Schemathesis provides an additional feature that allows you to use regular expressions to extract data from the string values of headers and query parameters.
+This can be particularly useful when the API response includes important information in these locations, and you need to use that data for further processing.
+
+Here's an example of how to extract the user ID from the ``Location`` header of a ``201 Created`` response:
+
+.. code-block::
+   :emphasize-lines: 12-12
+
+    paths:
+      /users:
+        post:
+          ...
+          responses:
+            '201':
+              ...
+              links:
+                GetUserByUserId:
+                  operationId: getUser
+                  parameters:
+                    userId: '$response.header.Location#regex:/users/(.+)'
+
+For example, if the ``Location`` header is ``/users/42``, the ``userId`` parameter will be set to ``42``.
+The regular expression should be a valid Python regular expression and should contain a single capturing group.
+
+If the regular expression does not match the value, the parameter will be set to empty.
 
 Open API links limitations
 --------------------------
@@ -503,9 +555,91 @@ following restriction:
   It is done due to ambiguity in the runtime expressions syntax, where ``}`` cannot be distinguished from an
   embedded runtime expression's closing bracket.
 
-**IMPORTANT**. The Open API standard defines ``requestBody`` keyword value in this way:
+For building ``requestBody``, the Open API standard only allows for literal values or expressions:
 
     A literal value or {expression} to use as a request body when calling the target operation.
 
-It means you cannot use multiple runtime expressions for different parameters, and you always have to provide either a literal
-or an expression.
+Schemathesis extends the Open API standard by allowing for the evaluation of runtime expressions within the ``requestBody`` object or array.
+
+For example, the following requestBody definition is valid:
+
+.. code-block:: json
+
+  {
+      "key": "$response.body#/key",
+      "items": ["$response.body#/first", "literal", 42]
+  }
+
+In this example, the ``$response.body#/key`` and ``$response.body#/first`` expressions are used to dynamically retrieve values from the response body. 
+
+If the response body is ``{"key": "foo", "first": "bar"}``, then the resulting payload will be:
+
+.. code-block:: json
+
+  {
+      "key": "foo",
+      "items": ["bar", "literal", 42]
+  }
+
+This allows for building dynamic payloads where nested items are not hardcoded but instead evaluated at runtime.
+
+**IMPORTANT**: Non-string object keys are converted to stringified JSON values during evaluation.
+
+By default, Schemathesis merges the evaluated structure with a generated value, giving the evaluated value precedence.
+
+State Machine Test Runner
+-------------------------
+
+If you need to run stateful tests without using ``pytest``, you can use the Schemathesis state machine test runner.
+Similarly to the default Schemathesis test runner, it allows for running state machines and reacting to events from them.
+
+A test run is the entire process of running the state machine, which consists of multiple test suites. 
+Each test suite contains multiple test scenarios and is executed until no new failures are found. 
+The test run continues until a test suite is executed without finding any new failures.
+
+A test run is the entire process of running the state machine. It starts by generating a new test suite and executing it. 
+If the test suite finishes with any new failures, Schemathesis generates another test suite and runs it. 
+This process continues until a generated test suite finishes successfully without finding any new failures
+
+Each test suite contains multiple test scenarios. Each test scenario is a sequence of steps generated by the state machine, where each step typically represents an API call. 
+
+.. important::
+
+    Each test scenario may include multiple API calls but is considered as a single test case by Hypothesis.
+    Therefore, the ``max_examples`` setting controls the number of test scenarios, not the number of API calls.
+
+The available events are:
+
+ - ``RunStarted`` - triggered before the entire test run starts.
+ - ``RunFinished`` - triggered after the entire test run finishes.
+ - ``SuiteStarted`` - triggered before each test suite starts.
+ - ``SuiteFinished`` - triggered after each test suite finishes, providing information about the failed checks.
+ - ``ScenarioStarted`` - triggered before each test scenario starts.
+ - ``ScenarioFinished`` - triggered after each test scenario finishes.
+ - ``StepStarted`` - triggered before each step in a test scenario is executed.
+ - ``StepFinished`` - triggered after each step in a test scenario is executed.
+ - ``Interrupted`` - triggered when the test run is interrupted by the user (e.g., via Ctrl+C).
+ - ``Errored`` - triggered when an unexpected error occurs during the test run.
+
+These events are primarily used for monitoring and reporting purposes, allowing you to track the progress of the state machine test runner. 
+They provide information about the current state of the test run but do not offer any control over the test execution.
+
+To collect the events you may use a "sink" that consumes the events and collects statistics about the test run.
+
+.. code-block:: python
+
+    import schemathesis
+    from schemathesis.stateful import events
+
+    schema = schemathesis.from_uri("http://127.0.0.1:8080/swagger.json")
+    state_machine = schema.as_state_machine()
+    sink = state_machine.sink()
+
+    runner = state_machine.runner()
+    for event in runner.execute():
+        sink.consume(event)
+        if isinstance(event, events.RunFinished):
+            print("Test run finished")
+    print("Duration:", sink.duration)
+    for failure in sink.failures:
+        print(failure)

{schemathesis-3.29.2 → schemathesis-3.30.0}/example/README.md

@@ -31,7 +31,7 @@ After setting up Docker and obtaining a copy of the project, you'll be ready to
 
 ## Command-line
 
-The examples below will the following environment variables and a shell alias to avoid visual clutter:
+The examples below will include the following environment variables and a shell alias to avoid visual clutter:
 
 ```shell
 export SCHEMA_URL="http://127.0.0.1:5123/openapi.json"

{schemathesis-3.29.2 → schemathesis-3.30.0}/example/requirements-pytest.txt

@@ -112,7 +112,7 @@ tomli-w==1.0.0
     # via schemathesis
 typing-extensions==4.8.0
     # via schemathesis
-urllib3==2.1.0
+urllib3==2.2.2
     # via requests
 werkzeug==3.0.3
     # via schemathesis

{schemathesis-3.29.2 → schemathesis-3.30.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "schemathesis"
-version = "3.29.2"
+version = "3.30.0"
 description = "Property-based testing framework for Open API and GraphQL based apps"
 keywords = ["pytest", "hypothesis", "openapi", "graphql", "testing"]
 authors = [{ name = "Dmitry Dygalo", email = "dmitry@dygalo.dev" }]

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/__init__.py

@@ -1,14 +1,14 @@
 from __future__ import annotations
+
 from typing import Any
 
-from . import auths, checks, experimental, contrib, fixups, graphql, hooks, runner, serializers, targets  # noqa: E402
+from . import auths, checks, contrib, experimental, fixups, graphql, hooks, runner, serializers, targets  # noqa: E402
 from ._lazy_import import lazy_import
-from .generation import DataGenerationMethod, GenerationConfig, HeaderConfig  # noqa: E402
 from .constants import SCHEMATHESIS_VERSION  # noqa: E402
+from .generation import DataGenerationMethod, GenerationConfig, HeaderConfig  # noqa: E402
 from .models import Case  # noqa: E402
 from .specs import openapi  # noqa: E402
 
-
 __version__ = SCHEMATHESIS_VERSION
 
 # Default loaders

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_compat.py

@@ -1,6 +1,6 @@
-from typing import Any, Type, Callable
-from ._lazy_import import lazy_import
+from typing import Any, Callable, Type
 
+from ._lazy_import import lazy_import
 
 __all__ = [  # noqa: F822
     "JSONMixin",

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_dependency_versions.py

@@ -1,16 +1,14 @@
 """Compatibility flags based on installed dependency versions."""
 
-from packaging import version
-
 from importlib import metadata
 
+from packaging import version
 
 WERKZEUG_VERSION = version.parse(metadata.version("werkzeug"))
 IS_WERKZEUG_ABOVE_3 = WERKZEUG_VERSION >= version.parse("3.0")
 IS_WERKZEUG_BELOW_2_1 = WERKZEUG_VERSION < version.parse("2.1.0")
 
 PYTEST_VERSION = version.parse(metadata.version("pytest"))
-IS_PYTEST_ABOVE_54 = PYTEST_VERSION >= version.parse("5.4.0")
 IS_PYTEST_ABOVE_7 = PYTEST_VERSION >= version.parse("7.0.0")
 IS_PYTEST_ABOVE_8 = PYTEST_VERSION >= version.parse("8.0.0")
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_hypothesis.py

@@ -10,6 +10,7 @@ import hypothesis
 from hypothesis import Phase
 from hypothesis import strategies as st
 from hypothesis.errors import HypothesisWarning, Unsatisfiable
+from hypothesis.internal.entropy import deterministic_PRNG
 from hypothesis.internal.reflection import proxies
 from jsonschema.exceptions import SchemaError
 
@@ -23,6 +24,11 @@ from .transports.content_types import parse_content_type
 from .transports.headers import has_invalid_characters, is_latin_1_encodable
 from .utils import GivenInput, combine_strategies
 
+# Forcefully initializes Hypothesis' global PRNG to avoid races that initilize it
+# if e.g. Schemathesis CLI is used with multiple workers
+with deterministic_PRNG():
+    pass
+
 
 def create_test(
     *,

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_lazy_import.py

@@ -1,4 +1,5 @@
 from __future__ import annotations
+
 from typing import Any, Callable
 
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_override.py

@@ -1,4 +1,5 @@
 from __future__ import annotations
+
 from dataclasses import dataclass
 from typing import TYPE_CHECKING, Optional
 

{schemathesis-3.29.2 → schemathesis-3.30.0}/src/schemathesis/_rate_limiter.py

@@ -3,4 +3,5 @@ from ._dependency_versions import IS_PYRATE_LIMITER_ABOVE_3
 if IS_PYRATE_LIMITER_ABOVE_3:
     from pyrate_limiter import Limiter, Rate, RateItem
 else:
-    from pyrate_limiter import Limiter, RequestRate as Rate
+    from pyrate_limiter import Limiter
+    from pyrate_limiter import RequestRate as Rate