schemathesis 3.27.0__tar.gz → 3.28.0__tar.gz

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
 
@@ -41,7 +41,7 @@ jobs:
     name: Documentation
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4.1.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
       - uses: ammaraskar/sphinx-action@master
@@ -66,7 +66,7 @@ jobs:
     name: Tests (Python ${{ matrix.python }} on ${{ matrix.os }} ${{ matrix.tox_env }})
     runs-on: ${{ matrix.os }}
     steps:
-      - uses: actions/checkout@v4.1.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
 
@@ -83,6 +83,6 @@ jobs:
         run: python -m tox
 
       - name: Upload coverage to Codecov
-        uses: codecov/codecov-action@v4.2.0
+        uses: codecov/codecov-action@v4.3.1
         with:
           token: ${{ secrets.CODECOV_TOKEN }}

{schemathesis-3.27.0 → schemathesis-3.28.0}/.github/workflows/codeql-analysis.yml

@@ -30,7 +30,7 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4.1.2
+        uses: actions/checkout@v4.1.4
         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.24.10
+        uses: github/codeql-action/init@v3.25.3
         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.24.10
+        uses: github/codeql-action/autobuild@v3.25.3
 
       # ℹ️ 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.24.10
+        uses: github/codeql-action/analyze@v3.25.3

{schemathesis-3.27.0 → schemathesis-3.28.0}/.github/workflows/codspeed.yml

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

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+        uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 0
       - name: Run commitsar

{schemathesis-3.27.0 → schemathesis-3.28.0}/.github/workflows/example-build.yml

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

{schemathesis-3.27.0 → schemathesis-3.28.0}/.github/workflows/master_update.yml

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

{schemathesis-3.27.0 → schemathesis-3.28.0}/.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
             tag-suffix: "-bookworm"
 
     steps:
-      - uses: actions/checkout@v4.1.2
+      - uses: actions/checkout@v4.1.4
 
       - 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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
 

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
 

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.27.0 → schemathesis-3.28.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.2
+      - uses: actions/checkout@v4.1.4
         with:
           fetch-depth: 1
           submodules: true

{schemathesis-3.27.0 → schemathesis-3.28.0}/.pre-commit-config.yaml

@@ -30,7 +30,7 @@ repos:
       - id: relint
 
   - repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v1.9.0
+    rev: v1.10.0
     hooks:
       - id: mypy
         exclude: ^(docs/|test/|test-corpus/|example/|benches/).*$
@@ -38,12 +38,12 @@ repos:
         additional_dependencies: [types-click, types-requests, types-PyYAML]
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.3.7
+    rev: v0.4.3
     hooks:
       - id: ruff-format
 
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.3.7
+    rev: v0.4.3
     hooks:
       - id: ruff
 

{schemathesis-3.27.0 → schemathesis-3.28.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: schemathesis
-Version: 3.27.0
+Version: 3.28.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
@@ -28,7 +28,6 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Topic :: Software Development :: Testing
 Requires-Python: >=3.8
-Requires-Dist: anyio<4
 Requires-Dist: backoff<3.0,>=2.1.2
 Requires-Dist: click<9.0,>=7.0
 Requires-Dist: colorama<1.0,>=0.4
@@ -44,7 +43,7 @@ Requires-Dist: pytest-subtests<0.8.0,>=0.2.1
 Requires-Dist: pytest<9,>=4.6.4
 Requires-Dist: pyyaml<7.0,>=5.1
 Requires-Dist: requests<3,>=2.22
-Requires-Dist: starlette-testclient<1
+Requires-Dist: starlette-testclient<1,>=0.4.1
 Requires-Dist: starlette<1,>=0.13
 Requires-Dist: tomli-w<2.0,>=1.0.0
 Requires-Dist: tomli<3.0,>=2.0.1
@@ -78,7 +77,7 @@ Requires-Dist: trustme<1.0,>=0.9.0; extra == 'tests'
 Description-Content-Type: text/markdown
 
 <p align="center">
-    <em>Schemathesis: catch crashes, validate specs, and save time</em>
+    <em>Schemathesis: Supercharge your API testing, catch bugs, and ensure compliance</em>
 </p>
 
 <p align="center">
@@ -110,29 +109,34 @@ Description-Content-Type: text/markdown
 
 ---
 
-## Why Schemathesis?
+## What is Schemathesis?
 
-Schemathesis is a tool that automates your API testing to catch crashes and spec violations. Built on top of the widely-used <a href="https://hypothesis.works/" target="_blank">Hypothesis</a> framework for property-based testing, it offers the following advantages:
+Schemathesis is a tool that levels-up your API testing by automating the process of finding crashes, uncovering bugs, and validating spec compliance. With Schemathesis, you can:
 
-🕒 **Time-Saving**
+🎯 **Catch Hard-to-Find Bugs**
 
-Automatically generates test cases, freeing you from manual test writing.
+- Uncover hidden crashes and edge cases that manual testing might miss
+- Identify spec violations and ensure your API adheres to its defined contract
 
-🔍 **Comprehensive**
+⚡ **Accelerate Testing Cycles**
 
-Utilizes fuzzing techniques to probe both common and edge-case scenarios, including those you might overlook.
+- Automatically generate a wide range of test cases based on your API schema
+- Save time and effort by eliminating the need for manual test case creation
 
-🛠️ **Flexible**
+🧩 **Integrate Seamlessly**
 
-Supports OpenAPI, GraphQL, and can work even with partially complete schemas. Only the parts describing data generation or responses are required.
+- Works with popular API formats such as OpenAPI, GraphQL.
+- Easily integrate into your existing testing pipeline and CI/CD workflows
 
-🎛️ **Customizable**
+🔧 **Customize and Extend**
 
-Customize the framework by writing Python extensions to modify almost any aspect of the testing process.
+- Tune the testing process to your specific requirements using Python extensions
+- Modify and enhance various aspects of the testing flow to suit your needs with rich configuration options
 
-🔄 **Reproducible**
+📊 **Gain Valuable Insights**
 
-Generates code samples to help you quickly replicate and investigate any failing test cases.
+- Get detailed reports and actionable insights to help you identify and fix issues quickly
+- Reproduce failing test cases effortlessly with generated code samples and cURL commands
 
 ## Quick Demo
 
@@ -310,6 +314,24 @@ This includes:
 
 To discuss a custom support arrangement that best suits your organization, please contact our support team at <a href="mailto:support@schemathesis.io">support@schemathesis.io</a>.
 
+## Acknowledgements
+
+Schemathesis is built on top of <a href="https://hypothesis.works/" target="_blank">Hypothesis</a>, a powerful property-based testing library for Python.
+
+## Who's Using Schemathesis?
+
+Schemathesis is used by a number of project and companies, including direct usage or integration into other tools:
+
+- Abstract Machines ([Magistrala](https://github.com/absmach/magistrala))
+- Bundesstelle für Open Data ([smard-api](https://github.com/bundesAPI/smard-api))
+- [CheckMK](https://github.com/Checkmk/checkmk)
+- HXSecurity ([DongTai](https://github.com/HXSecurity/DongTai))
+- Netflix ([Dispatch](https://github.com/Netflix/dispatch))
+- [Pixie](https://github.com/pixie-io/pixie)
+- [Qdrant](https://github.com/qdrant/qdrant)
+- Spotify ([Backstage](https://github.com/backstage/backstage))
+- WordPress ([OpenVerse](https://github.com/WordPress/openverse))
+
 ## Additional content
 
 ### Papers

{schemathesis-3.27.0 → schemathesis-3.28.0}/README.md

@@ -1,5 +1,5 @@
 <p align="center">
-    <em>Schemathesis: catch crashes, validate specs, and save time</em>
+    <em>Schemathesis: Supercharge your API testing, catch bugs, and ensure compliance</em>
 </p>
 
 <p align="center">
@@ -31,29 +31,34 @@
 
 ---
 
-## Why Schemathesis?
+## What is Schemathesis?
 
-Schemathesis is a tool that automates your API testing to catch crashes and spec violations. Built on top of the widely-used <a href="https://hypothesis.works/" target="_blank">Hypothesis</a> framework for property-based testing, it offers the following advantages:
+Schemathesis is a tool that levels-up your API testing by automating the process of finding crashes, uncovering bugs, and validating spec compliance. With Schemathesis, you can:
 
-🕒 **Time-Saving**
+🎯 **Catch Hard-to-Find Bugs**
 
-Automatically generates test cases, freeing you from manual test writing.
+- Uncover hidden crashes and edge cases that manual testing might miss
+- Identify spec violations and ensure your API adheres to its defined contract
 
-🔍 **Comprehensive**
+⚡ **Accelerate Testing Cycles**
 
-Utilizes fuzzing techniques to probe both common and edge-case scenarios, including those you might overlook.
+- Automatically generate a wide range of test cases based on your API schema
+- Save time and effort by eliminating the need for manual test case creation
 
-🛠️ **Flexible**
+🧩 **Integrate Seamlessly**
 
-Supports OpenAPI, GraphQL, and can work even with partially complete schemas. Only the parts describing data generation or responses are required.
+- Works with popular API formats such as OpenAPI, GraphQL.
+- Easily integrate into your existing testing pipeline and CI/CD workflows
 
-🎛️ **Customizable**
+🔧 **Customize and Extend**
 
-Customize the framework by writing Python extensions to modify almost any aspect of the testing process.
+- Tune the testing process to your specific requirements using Python extensions
+- Modify and enhance various aspects of the testing flow to suit your needs with rich configuration options
 
-🔄 **Reproducible**
+📊 **Gain Valuable Insights**
 
-Generates code samples to help you quickly replicate and investigate any failing test cases.
+- Get detailed reports and actionable insights to help you identify and fix issues quickly
+- Reproduce failing test cases effortlessly with generated code samples and cURL commands
 
 ## Quick Demo
 
@@ -231,6 +236,24 @@ This includes:
 
 To discuss a custom support arrangement that best suits your organization, please contact our support team at <a href="mailto:support@schemathesis.io">support@schemathesis.io</a>.
 
+## Acknowledgements
+
+Schemathesis is built on top of <a href="https://hypothesis.works/" target="_blank">Hypothesis</a>, a powerful property-based testing library for Python.
+
+## Who's Using Schemathesis?
+
+Schemathesis is used by a number of project and companies, including direct usage or integration into other tools:
+
+- Abstract Machines ([Magistrala](https://github.com/absmach/magistrala))
+- Bundesstelle für Open Data ([smard-api](https://github.com/bundesAPI/smard-api))
+- [CheckMK](https://github.com/Checkmk/checkmk)
+- HXSecurity ([DongTai](https://github.com/HXSecurity/DongTai))
+- Netflix ([Dispatch](https://github.com/Netflix/dispatch))
+- [Pixie](https://github.com/pixie-io/pixie)
+- [Qdrant](https://github.com/qdrant/qdrant)
+- Spotify ([Backstage](https://github.com/backstage/backstage))
+- WordPress ([OpenVerse](https://github.com/WordPress/openverse))
+
 ## Additional content
 
 ### Papers

{schemathesis-3.27.0 → schemathesis-3.28.0}/docs/auth.rst

@@ -139,16 +139,18 @@ To use your custom authentication mechanism in the Schemathesis CLI, you need to
         # Here goes your implementation
         ...
 
-Put the code above to the ``hooks.py`` file and extend your command via the ``SCHEMATHESIS_HOOKS`` environment variable:
+Then put your code into a Python file (for example, ``my_file.py``) and set the ``SCHEMATHESIS_HOOKS`` environment variable to point to it:
 
 .. code:: bash
 
-    $ SCHEMATHESIS_HOOKS=hooks
-    $ st run ...
+    SCHEMATHESIS_HOOKS=my_file
+    st run http://127.0.0.1/openapi.yaml
+
+That is it! Now Schemathesis will use your custom authentication mechanism for all tests.
 
 .. note::
 
-    You can take a look at how to extend CLI :ref:`here <extend-cli>`
+    The registration process is the same as for any other extension, and you can find more details on how to extend Schemathesis in the :ref:`Extending Schemathesis <enabling-extensions>` section.
 
 Using in Python tests
 ~~~~~~~~~~~~~~~~~~~~~

{schemathesis-3.27.0 → schemathesis-3.28.0}/docs/changelog.rst

@@ -1,9 +1,47 @@
 Changelog
 =========
 
-:version:`Unreleased <v3.27.0...HEAD>` - TBD
+:version:`Unreleased <v3.28.0...HEAD>` - TBD
 --------------------------------------------
 
+.. _v3.28.0:
+
+:version:`3.28.0 <v3.27.1...v3.28.0>` - 2024-05-10
+--------------------------------------------------
+
+**Added**
+
+- ``Request.deserialize_body`` and ``Response.deserialize_body`` helper methods to deserialize payloads to bytes from Base 64.
+- Support for ``multipart/mixed`` media type.
+
+**Changed**
+
+- Do not show suggestion to show a traceback on Hypothesis' ``Unsatisfiable`` error.
+- Clarify error message on unsupported recursive references.
+- Report more details on some internal errors instead of "Unknown Schema Error".
+- Update error message on why Schemathesis can't generate test cases for some API operations.
+
+**Fixed**
+
+- Internal error on Windows when the CLI output is redirected to a file and code samples contain non CP1252 characters.
+- Properly check for nested recursive references inside combinators. This makes Schemathesis work with more schemas with recursive references.
+
+.. _v3.27.1:
+
+:version:`3.27.1 <v3.27.0...v3.27.1>` - 2024-04-29
+--------------------------------------------------
+
+**Added**
+
+- ``GenerationConfig.headers.strategy`` attribute for customizing header generation. :issue:`2137`
+- Support for ``python -m schemathesis.cli``. :issue:`2142`
+- Support for ``anyio>=4.0``. :issue:`2081`
+
+**Fixed**
+
+- Supporting non-Starlette ASGI apps. :issue:`2136`
+- Missing version metadata in ASGI client causing errors with ASGI3-only apps. :issue:`2136`
+
 .. _v3.27.0:
 
 :version:`3.27.0 <v3.26.2...v3.27.0>` - 2024-04-14

{schemathesis-3.27.0 → schemathesis-3.28.0}/docs/cli.rst

@@ -531,25 +531,29 @@ Extending CLI
 -------------
 
 To fit Schemathesis to your workflows, you might want to extend it with your custom checks or setup environment before the test run.
-Schemathesis can load your Python code via the ``SCHEMATHESIS_HOOKS`` environment variable:
 
-.. code:: bash
+Extensions should be placed in a separate Python module. 
+Then, Schemathesis should be informed about this module via the ``SCHEMATHESIS_HOOKS`` environment variable:
 
-    $ SCHEMATHESIS_HOOKS=test.setup
-    $ st run https://example.com/api/swagger.json
+.. code:: bash
 
-**NOTE**. This option should be passed before the ``run`` subcommand.
+    export SCHEMATHESIS_HOOKS=myproject.tests.hooks
+    st run http://127.0.0.1/openapi.yaml
 
 Also, depending on your setup, you might need to run this command with a custom ``PYTHONPATH`` environment variable like this:
 
 .. code:: bash
 
-    $ PYTHONPATH=$(pwd)
-    $ SCHEMATHESIS_HOOKS=test.setup
-    $ st run https://example.com/api/swagger.json
+    export PYTHONPATH=$(pwd)
+    export SCHEMATHESIS_HOOKS=myproject.tests.hooks
+    st run https://example.com/api/swagger.json
 
 The passed value will be treated as an importable Python path and imported before the test run.
 
+.. note::
+
+    You can find more details on how to extend Schemathesis in the :ref:`Extending Schemathesis <enabling-extensions>` section.
+
 Registering custom checks
 ~~~~~~~~~~~~~~~~~~~~~~~~~
 

{schemathesis-3.27.0 → schemathesis-3.28.0}/docs/extending.rst

@@ -97,19 +97,36 @@ They execute in the order they are defined, with globally defined hooks executin
     Be mindful of the sequence in which hooks are applied. The order can significantly impact the generated test data and subsequent API calls during testing. 
     Always validate the test data and requests to ensure that hooks are applied in the intended order and manner.
 
-Enabling and Organizing Hooks
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+.. _enabling-extensions:
 
-For Schemathesis to utilize your custom hooks, they need to be properly organized and enabled.
+Enabling Extensions
+~~~~~~~~~~~~~~~~~~~
 
-For **CLI** usage, hooks should be placed in a separate module. 
-Schemathesis should be directed to this module through the ``SCHEMATHESIS_HOOKS`` environment variable:
+For Schemathesis to utilize your custom hooks or other extensions, they need to be properly enabled.
+
+For **CLI** usage, extensions should be placed in a separate Python module. 
+Then, Schemathesis should be informed about this module via the ``SCHEMATHESIS_HOOKS`` environment variable:
 
 .. code:: bash
 
-    SCHEMATHESIS_HOOKS=myproject.tests.hooks
+    export SCHEMATHESIS_HOOKS=myproject.tests.hooks
     st run http://127.0.0.1/openapi.yaml
 
+Also, depending on your setup, you might need to run this command with a custom ``PYTHONPATH`` environment variable like this:
+
+.. code:: bash
+
+    export PYTHONPATH=$(pwd)
+    export SCHEMATHESIS_HOOKS=myproject.tests.hooks
+    st run https://example.com/api/swagger.json
+
+In the example above, the module is located at ``myproject/tests/hooks.py`` and the environment variable contains 
+a path that could be used as an import in Python.
+
+.. note::
+
+    The name of the module is arbitrary but make sure it is a valid Python module name. Usually it is sufficient to put all your extensions in the ``hooks.py`` file in the current directory.
+
 If you're using Schemathesis in Python tests, ensure to define your hooks in the test setup code.
 
 Filtering Data
@@ -651,6 +668,51 @@ In the example above, when Schemathesis detects a string with the "card_number"
 
 For more details about creating strategies, refer to the `Hypothesis documentation <https://hypothesis.readthedocs.io/en/latest/data.html>`_.
 
+Adjusting header generation
+---------------------------
+
+By default, Schemathesis generates headers based on the schema definition falling back to the set of characters defined in `RFC 7230 <https://datatracker.ietf.org/doc/html/rfc7230#section-3.2>`_, but you can adjust this behavior to suit your needs.
+
+To customize header generation, you can extend the ``GenerationConfig`` class and modify its ``headers`` attribute. 
+The ``headers`` attribute accepts a ``HeaderConfig`` object, which allows you to specify a custom Hypothesis strategy for generating header values.
+
+Here's an example of how you can adjust header generation:
+
+.. code-block:: python
+
+    import schemathesis
+    from schemathesis import GenerationConfig, HeaderConfig
+    from hypothesis import strategies as st
+
+    schema = schemathesis.from_uri(
+        "https://example.schemathesis.io/openapi.json",
+        generation_config=GenerationConfig(
+            headers=HeaderConfig(
+                strategy=st.text(
+                    alphabet=st.characters(
+                        min_codepoint=1, 
+                        max_codepoint=127,
+                    ).map(str.strip)
+                )
+            )
+        ),
+    )
+
+In the code above, we use the ``st.text`` strategy from Hypothesis to restrict the characters used in the generated headers to codepoints 1 to 127.
+
+Alternatively, you can customize header generation using the ``after_load_schema`` hook:
+
+.. code-block:: python
+
+    import schemathesis
+    from hypothesis import strategies as st
+
+    @schemathesis.hook
+    def after_load_schema(context, schema) -> None:
+        schema.generation_config.headers.strategy = st.text(
+            alphabet=st.characters(min_codepoint=1, max_codepoint=127)
+        )
+
 Generating payloads for unknown media types
 -------------------------------------------
 

{schemathesis-3.27.0 → schemathesis-3.28.0}/docs/index.rst

@@ -1,18 +1,40 @@
 Welcome to Schemathesis!
 ========================
 
-Schemathesis is a tool that automates API testing by leveraging API specs as a blueprints for generating test cases.
+Schemathesis is a tool that levels-up your API testing by leveraging API specs as a blueprints for generating test cases.
 It focuses on testing for general properties — such as ensuring no input leads to server errors and all responses adhere to the API spec — rather than just checking specific input-output combinations.
 
 This approach broadens your testing suite's capability to detect a wide range of potential issues, from trivial bugs to critical vulnerabilities.
 
-Built on top of the widely-used `Hypothesis <http://hypothesis.works/>`_ framework for property-based testing, it offers the following advantages:
+With Schemathesis, you can:
 
-- 🕒 **Time-Saving**: Automatically generates test cases, freeing you from manual test writing.
-- 🔍 **Comprehensive**: Utilizes fuzzing techniques for both common and edge-case scenarios.
-- 🛠️ **Flexible**: Supports OpenAPI and GraphQL. Operates even with partially complete schemas.
-- 🎛️ **Customizable**: Extend almost any aspect of the testing process through Python.
-- 🔄 **Reproducible**: Generates code samples for quick replication of any failing test cases.
+🎯 **Catch Hard-to-Find Bugs**
+
+- Uncover hidden crashes and edge cases that manual testing might miss
+- Identify spec violations and ensure your API adheres to its defined contract
+
+⚡ **Accelerate Testing Cycles**
+
+- Automatically generate a wide range of test cases based on your API schema
+- Save time and effort by eliminating the need for manual test case creation
+
+🧩 **Integrate Seamlessly**
+
+- Works with popular API formats such as OpenAPI, GraphQL.
+- Easily integrate into your existing testing pipeline and CI/CD workflows
+
+🔧 **Customize and Extend**
+
+- Tune the testing process to your specific requirements using Python extensions
+- Modify and enhance various aspects of the testing flow to suit your needs with rich configuration options
+
+📊 **Gain Valuable Insights**
+
+- Get detailed reports and actionable insights to help you identify and fix issues quickly
+- Reproduce failing test cases effortlessly with generated code samples and cURL commands
+
+How it works?
+-------------
 
 Here’s a simplified overview of how Schemathesis works:
 

{schemathesis-3.27.0 → schemathesis-3.28.0}/example/requirements-app.txt

@@ -18,7 +18,7 @@ greenlet==3.0.1
     # via sqlalchemy
 itsdangerous==2.1.2
     # via flask
-jinja2==3.1.3
+jinja2==3.1.4
     # via flask
 markupsafe==2.1.3
     # via
@@ -28,5 +28,5 @@ sqlalchemy==1.4.50
     # via
     #   -r requirements-app.in
     #   flask-sqlalchemy
-werkzeug==3.0.1
+werkzeug==3.0.3
     # via flask