pytest-httpchain 0.1.1__tar.gz → 0.2.0__tar.gz

{pytest_httpchain-0.1.1 → pytest_httpchain-0.2.0}/PKG-INFO

@@ -1,10 +1,11 @@
 Metadata-Version: 2.4
 Name: pytest-httpchain
-Version: 0.1.1
+Version: 0.2.0
 Summary: pytest plugin for HTTP testing using JSON files
 Keywords: testing,pytest,requests
 Author: Alexander Eresov
 Author-email: Alexander Eresov <aeresov@gmail.com>
+License-Expression: MIT
 License-File: LICENSE
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Framework :: Pytest
@@ -13,11 +14,12 @@ Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development :: Testing
+Requires-Dist: httpx[http2]>=0.27.0
 Requires-Dist: pydantic>=2.11.7
+Requires-Dist: pyrate-limiter>=3.0.0
 Requires-Dist: pytest-httpchain-jsonref
 Requires-Dist: pytest-httpchain-models
 Requires-Dist: pytest-order>=1.3.0
-Requires-Dist: rich>=13.7.0
 Requires-Dist: pytest-httpchain-mcp ; extra == 'mcp'
 Requires-Python: >=3.13, <4.0
 Provides-Extra: mcp
@@ -33,7 +35,7 @@ A pytest plugin for testing HTTP endpoints.
 
 ## Overview
 
-`pytest-httpchain` is an integration testing framework for HTTP APIs based on battle-hardened [requests](https://requests.readthedocs.io) lib.  
+`pytest-httpchain` is an integration testing framework for HTTP APIs based on [httpx](https://www.python-httpx.org) lib.  
 It aims at helping with common HTTP API testing scenarios, where user needs to make several calls in specific order using data obtained along the way, like auth tokens or resource ids.
 
 ## Installation
@@ -60,9 +62,7 @@ The following optional dependencies are available:
 
 ### Pytest integration
 
-Most of pytest magic can be used: markers, fixtures, other plugins.  
-
-> NOTE: parametrization is not yet implemented, therefore `parametrize` marker won't have any effect.
+Most of pytest magic can be used: markers, fixtures, other plugins.
 
 ### Declarative format
 
@@ -89,6 +89,7 @@ Values from common data context also might be verified during verified/asserted.
 -   to extract data from HTTP response
 -   to verify HTTP response and values in common data context
 -   to provide [custom authentication for requests](https://requests.readthedocs.io/en/latest/user/advanced/#custom-authentication)
+-   to call in substitution expressions
 
 ### JMESPath support
 
@@ -114,9 +115,13 @@ def now_utc():
 
 ```json
 {
-    "vars": {
-        "user_id": 1
-    },
+    "substitutions": [
+        {
+            "vars": {
+                "user_id": 1
+            }
+        }
+    ],
     "stages": [
         {
             "name": "get_user",
@@ -131,7 +136,7 @@ def now_utc():
                 },
                 {
                     "save": {
-                        "vars": {
+                        "jmespath": {
                             "user_name": "user.name"
                         }
                     }
@@ -186,7 +191,7 @@ Scenario we created:
     url is assembled using `user_id` variable from common data context  
     we create JSON body in place using values from common data context, note that `now_utc` is converted to string in place  
     HTTP PUT call with body is made  
-    we verify the call returned code 200  
+    we verify the call returned code 200
 -   **cleanup**  
     finalizing call meant for graceful exit  
     `always_run` parameter means this stage will be executed regardless of errors in previous stages
@@ -238,8 +243,9 @@ The MCP server provides:
 
 ## Thanks
 
-`pytest-httpchain` was heavily inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
-[requests](https://requests.readthedocs.io) does the comms.  
-[Pydantic](https://docs.pydantic.dev) keeps the structure.  
-[pytest-order](https://github.com/pytest-dev/pytest-order) powers the chaining.  
-[pytest-datadir](https://github.com/gabrielcnr/pytest-datadir) saved me a lot of elbow grease.  
+`pytest-httpchain` was inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
+[httpx](https://www.python-httpx.org) does comms.  
+[Pydantic](https://docs.pydantic.dev) keeps structure.  
+[simpleeval](https://github.com/danthedeckie/simpleeval) powers templates.  
+[pytest-order](https://github.com/pytest-dev/pytest-order) sorts chain.  
+[pytest-datadir](https://github.com/gabrielcnr/pytest-datadir) saved me a lot of elbow grease while testing.

{pytest_httpchain-0.1.1 → pytest_httpchain-0.2.0}/README.md

@@ -8,7 +8,7 @@ A pytest plugin for testing HTTP endpoints.
 
 ## Overview
 
-`pytest-httpchain` is an integration testing framework for HTTP APIs based on battle-hardened [requests](https://requests.readthedocs.io) lib.  
+`pytest-httpchain` is an integration testing framework for HTTP APIs based on [httpx](https://www.python-httpx.org) lib.  
 It aims at helping with common HTTP API testing scenarios, where user needs to make several calls in specific order using data obtained along the way, like auth tokens or resource ids.
 
 ## Installation
@@ -35,9 +35,7 @@ The following optional dependencies are available:
 
 ### Pytest integration
 
-Most of pytest magic can be used: markers, fixtures, other plugins.  
-
-> NOTE: parametrization is not yet implemented, therefore `parametrize` marker won't have any effect.
+Most of pytest magic can be used: markers, fixtures, other plugins.
 
 ### Declarative format
 
@@ -64,6 +62,7 @@ Values from common data context also might be verified during verified/asserted.
 -   to extract data from HTTP response
 -   to verify HTTP response and values in common data context
 -   to provide [custom authentication for requests](https://requests.readthedocs.io/en/latest/user/advanced/#custom-authentication)
+-   to call in substitution expressions
 
 ### JMESPath support
 
@@ -89,9 +88,13 @@ def now_utc():
 
 ```json
 {
-    "vars": {
-        "user_id": 1
-    },
+    "substitutions": [
+        {
+            "vars": {
+                "user_id": 1
+            }
+        }
+    ],
     "stages": [
         {
             "name": "get_user",
@@ -106,7 +109,7 @@ def now_utc():
                 },
                 {
                     "save": {
-                        "vars": {
+                        "jmespath": {
                             "user_name": "user.name"
                         }
                     }
@@ -161,7 +164,7 @@ Scenario we created:
     url is assembled using `user_id` variable from common data context  
     we create JSON body in place using values from common data context, note that `now_utc` is converted to string in place  
     HTTP PUT call with body is made  
-    we verify the call returned code 200  
+    we verify the call returned code 200
 -   **cleanup**  
     finalizing call meant for graceful exit  
     `always_run` parameter means this stage will be executed regardless of errors in previous stages
@@ -213,8 +216,9 @@ The MCP server provides:
 
 ## Thanks
 
-`pytest-httpchain` was heavily inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
-[requests](https://requests.readthedocs.io) does the comms.  
-[Pydantic](https://docs.pydantic.dev) keeps the structure.  
-[pytest-order](https://github.com/pytest-dev/pytest-order) powers the chaining.  
-[pytest-datadir](https://github.com/gabrielcnr/pytest-datadir) saved me a lot of elbow grease.  
+`pytest-httpchain` was inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
+[httpx](https://www.python-httpx.org) does comms.  
+[Pydantic](https://docs.pydantic.dev) keeps structure.  
+[simpleeval](https://github.com/danthedeckie/simpleeval) powers templates.  
+[pytest-order](https://github.com/pytest-dev/pytest-order) sorts chain.  
+[pytest-datadir](https://github.com/gabrielcnr/pytest-datadir) saved me a lot of elbow grease while testing.

{pytest_httpchain-0.1.1 → pytest_httpchain-0.2.0}/pyproject.toml

@@ -1,18 +1,20 @@
 [project]
 name = "pytest-httpchain"
-version = "0.1.1"
+version = "0.2.0"
 description = "pytest plugin for HTTP testing using JSON files"
 readme = "README.md"
 requires-python = ">=3.13,<4.0"
 authors = [{ name = "Alexander Eresov", email = "aeresov@gmail.com" }]
 dependencies = [
+    "httpx[http2]>=0.27.0",
     "pydantic>=2.11.7",
+    "pyrate-limiter>=3.0.0",
     "pytest-httpchain-jsonref",
     "pytest-httpchain-models",
     "pytest-order>=1.3.0",
-    "rich>=13.7.0",
 ]
 keywords = ["testing", "pytest", "requests"]
+license = "MIT"
 license-files = ["LICENSE"]
 classifiers = [
     "Development Status :: 5 - Production/Stable",
@@ -31,9 +33,10 @@ mcp = ["pytest-httpchain-mcp"]
 dev = [
     "flask-httpauth>=4.8.0",
     "http-server-mock>=1.7",
-    "pytest-xdist>=3.8.0",
-    "responses>=0.25.7",
     "ruff>=0.12.1",
+    "pytest-cov>=6.0.0",
+    "coverage[toml]>=7.0",
+    "pytest-datadir>=1.7.2",
 ]
 docs = [
     "mkdocs>=1.6.1",
@@ -43,7 +46,7 @@ docs = [
 ]
 
 [tool.uv]
-default-groups = ["docs"]
+default-groups = ["dev", "docs"]
 
 [tool.uv.workspace]
 members = ["packages/*"]
@@ -85,10 +88,10 @@ ignore = []
 [tool.ruff.lint.isort]
 known-first-party = ["tests", "utils"]
 
-[tool.pytest.ini_options]
+[tool.pytest]
+minversion = "9.0"
 log_cli = true
 log_cli_level = "INFO"
-# testpaths = ["tests"]
 norecursedirs = ["examples"]
 pytester_example_dir = "tests/integration/examples"
 addopts = ["--log-disable=werkzeug", "--import-mode=importlib"]
@@ -110,3 +113,19 @@ reportMissingTypeStubs = false
 reportExplicitAny = false
 typeCheckingMode = "off"
 pythonPlatform = "Linux"
+
+[tool.coverage.run]
+source = [
+    "src",
+    "packages/pytest-httpchain-jsonref/src",
+    "packages/pytest-httpchain-templates/src",
+    "packages/pytest-httpchain-mcp/src",
+    "packages/pytest-httpchain-models/src",
+    "packages/pytest-httpchain-userfunc/src",
+]
+branch = true
+
+[tool.coverage.report]
+precision = 2
+show_missing = true
+skip_covered = false

pytest_httpchain-0.2.0/src/pytest_httpchain/__init__.py

@@ -0,0 +1,23 @@
+"""pytest-httpchain: Declarative HTTP API integration testing.
+
+This pytest plugin enables declarative HTTP API integration testing using JSON files.
+Test scenarios are defined with $ref support, template expressions ({{ expr }}),
+and multi-stage request chaining.
+
+Example test file (test_api.http.json):
+    {
+        "description": "API integration test",
+        "stages": [
+            {
+                "name": "Get user",
+                "request": {
+                    "method": "GET",
+                    "url": "https://api.example.com/users/1"
+                },
+                "response": [
+                    {"verify": {"status": 200}}
+                ]
+            }
+        ]
+    }
+"""