pytest-httpchain 0.2.1__tar.gz → 0.3.0__tar.gz

{pytest_httpchain-0.2.1 → pytest_httpchain-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytest-httpchain
-Version: 0.2.1
+Version: 0.3.0
 Summary: pytest plugin for HTTP testing using JSON files
 Keywords: testing,pytest,requests
 Author: Alexander Eresov
@@ -19,10 +19,10 @@ 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-httpchain-templates
 Requires-Dist: pytest-order>=1.3.0
-Requires-Dist: pytest-httpchain-mcp ; extra == 'mcp'
+Requires-Dist: typer>=0.16.0
 Requires-Python: >=3.13, <4.0
-Provides-Extra: mcp
 Description-Content-Type: text/markdown
 
 [![image](https://img.shields.io/pypi/v/pytest-httpchain)](https://pypi.python.org/pypi/pytest-httpchain)
@@ -38,66 +38,44 @@ A pytest plugin for testing HTTP endpoints.
 `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
-
-Install normally via package manager of your choice from PyPi:
-
-```bash
-pip install pytest-httpchain
-```
-
-or directly from Github, in case you need a particular ref:
-
-```bash
-pip install 'git+https://github.com/aeresov/pytest-httpchain@main'
-```
+## Why pytest-httpchain?
 
-### Optional dependencies
+Testing HTTP APIs with plain pytest often leads to these pain points:
 
-The following optional dependencies are available:
+-   **Boilerplate accumulates** — Every test repeats the same setup: create client, set headers, make request, parse response, assert. The actual test intent gets buried.
+-   **Data threading is manual** — When one call returns a token or ID needed by the next, you end up with fragile helper functions passing state around.
+-   **Common patterns get copy-pasted** — Auth flows, base URLs, shared headers end up duplicated across test files. Fixtures might help, but they are not designed for that.
+-   **Code reviews are noisy** — The actual test logic is rarely clear because of all the boilerplate and helpers, following changes gets overwhelming quickly.
 
--   `mcp`: installs MCP server package and its starting script. Details in [MCP Server](#mcp-server).
+`pytest-httpchain` offers a more structured approach.
 
 ## Features
 
-### Pytest integration
+### Declarative JSON format
 
-Most of pytest magic can be used: markers, fixtures, other plugins.
+Test scenarios are JSON documents that describe _what_ to test, not _how_. No setup code to scroll through — the request and assertions are right there.
 
-### Declarative format
+### `$ref` with deep merging
 
-Test scenarios are written declaratively in JSON files.  
-`pytest-httpchain` supports JSONRef, so use can reuse arbitrary parts of your scenarios with `$ref` directive.  
-Properties are merged in a greedy way with type checking.
+Reuse arbitrary parts of your scenarios with JSONRef. Properties merge with type checking, so you can compose scenarios from shared fragments (auth flows, common headers, base URLs).
 
-### Multi-stage tests
+### Multi-stage execution
 
-Each test scenario contains 1+ stages; each stage is a single HTTP call.  
-`pytest-httpchain` executes stages in the order they are listed in scenario file; one stage failure stops the execution chain.
+Each scenario contains 1+ stages executed in order. One stage failure stops the chain. Use `always_run` for cleanup stages that should execute regardless.
 
-### Common data context and variable substitution
+### Common data context
 
-`pytest-httpchain` maintains key-value data storage throughout the execution.  
-This storage ("common data context") is populated with declared variables, fixtures and data saved by stages. The data remains there throughout the scenario execution.  
-Writing scenarios, you can use Jinja-style expressions like `"{{ var }}"` for JSON values. `pytest-httpchain` does variable substitution dynamically right before executing a stage, and uses common data context keys as variables in these expressions.  
-Values from common data context also might be verified during verified/asserted.
+A key-value store persists throughout scenario execution. Variables, fixtures, and saved response data all live here. Use template expressions (`{{ var }}`) anywhere in your requests — substitution happens dynamically before each stage.
 
-### User functions
+### Response processing
 
-`pytest-httpchain` can import and call regular python functions:
+-   **JMESPath** — Extract values from JSON responses directly
+-   **JSON Schema** — Validate response structure against a schema
+-   **User functions** — Call Python functions for custom extraction, verification, or [authentication](https://requests.readthedocs.io/en/latest/user/advanced/#custom-authentication)
 
--   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
+### Full pytest integration
 
-### JMESPath support
-
-`pytest-httpchain` can extract values from JSON responses using JMESPath expressions directly.
-
-### JSON schema support
-
-`pytest-httpchain` can verify JSON reponses against user-defined JSON schema.
+Markers, fixtures, parametrization, and other plugins work as expected. You're not locked into a separate ecosystem.
 
 ## Quick Start
 
@@ -122,9 +100,8 @@ def now_utc():
             }
         }
     ],
-    "stages": [
-        {
-            "name": "get_user",
+    "stages": {
+        "get_user": {
             "request": {
                 "url": "https://api.example.com/users/{{ user_id }}"
             },
@@ -143,8 +120,7 @@ def now_utc():
                 }
             ]
         },
-        {
-            "name": "update_user",
+        "update_user": {
             "fixtures": ["now_utc"],
             "request": {
                 "url": "https://api.example.com/users/{{ user_id }}",
@@ -166,15 +142,14 @@ def now_utc():
                 }
             ]
         },
-        {
-            "name": "cleanup",
+        "cleanup": {
             "always_run": true,
             "request": {
                 "url": "https://api.example.com/cleanup",
                 "method": "POST"
             }
         }
-    ]
+    }
 }
 ```
 
@@ -196,54 +171,74 @@ Scenario we created:
     finalizing call meant for graceful exit  
     `always_run` parameter means this stage will be executed regardless of errors in previous stages
 
-For detailed examples see [USAGE.md](USAGE.md).
+For detailed usage guide see the [full documentation](https://aeresov.github.io/pytest-httpchain).
+
+## Installation
+
+Install normally via package manager of your choice from PyPi:
+
+```bash
+pip install pytest-httpchain
+```
+
+or directly from Github, in case you need a particular ref:
+
+```bash
+pip install 'git+https://github.com/aeresov/pytest-httpchain@main'
+```
 
 ## Configuration
 
--   Test file discovery is based on this name pattern: `test_<name>.<suffix>.json`.  
+-   Test file discovery is based on this name pattern: `test_<name>.<suffix>.json`.
     The `suffix` is configurable as pytest ini option, default value is **http**.
--   `$ref` instructions can point to other files; absolute and relative paths are supported.  
+-   `$ref` instructions can point to other files; absolute and relative paths are supported.
     You can limit the depth of relative path traversal using `ref_parent_traversal_depth` ini option, default value is **3**.
+-   Template expressions support list/dict comprehensions. You can limit the maximum comprehension length using `max_comprehension_length` ini option, default value is **50000**.
+-   Parallel stage iterations (repeat/foreach) have a safety limit configurable via `max_parallel_iterations` ini option, default value is **10000**.
 
-## MCP Server
+## AI agent support
 
-`pytest-httpchain` includes an MCP (Model Context Protocol) server to aid AI code assistants.
+`pytest-httpchain` ships tooling to help AI coding agents (and humans) author and check test scenarios.
 
-### Installation
+### Claude Code skill
 
-The optional dependency `mcp` installs MCP server's package and `pytest-httpchain-mcp` script.  
-Use this script as call target for your MCP configuration.
+Install the authoring skill into your project (or `--global` for personal scope):
 
-Claude Code `.mcp.json` example:
+```bash
+uvx pytest-httpchain install
+```
 
-```json
-{
-    "mcpServers": {
-        "pytest-httpchain": {
-            "type": "stdio",
-            "command": "uv",
-            "args": ["run", "pytest-httpchain-mcp"],
-            "env": {}
-        }
-    }
-}
+This writes `.claude/skills/pytest-httpchain/SKILL.md` with guidance for writing scenarios.
+
+### Scenario validation
+
+Validate scenario files for structure and common problems — undefined variables, duplicate stage names, fixture/variable conflicts, stages with no assertions:
+
+```bash
+uvx pytest-httpchain validate tests/test_login.http.json
 ```
 
-### Features
+It exits non-zero when any file is invalid, so it doubles as a CI gate. The same checks also run automatically at **pytest collection time** — semantic errors fail collection and warnings are reported — so `pytest --collect-only` validates every scenario in your suite.
 
-The MCP server provides:
+### Editor schema
 
--   **Scenario validation** - validate test scenario and scan for possible problems
+A JSON Schema is published for as-you-type validation and autocomplete. Reference it from your test files:
+
+```json
+{
+    "$schema": "https://aeresov.github.io/pytest-httpchain/schema/scenario.schema.json"
+}
+```
 
 ## Documentation
 
--   [Usage Examples](USAGE.md) - Practical code examples
--   [Full Documentation](https://aeresov.github.io/pytest-httpchain) - Complete guide
+-   [Full Documentation](https://aeresov.github.io/pytest-httpchain) - Complete usage guide
 -   [Changelog](CHANGELOG.md) - Release notes
 
 ## Thanks
 
-`pytest-httpchain` was inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
+This project 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_httpchain-0.2.1 → pytest_httpchain-0.3.0}/README.md

@@ -11,66 +11,44 @@ A pytest plugin for testing HTTP endpoints.
 `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
-
-Install normally via package manager of your choice from PyPi:
-
-```bash
-pip install pytest-httpchain
-```
-
-or directly from Github, in case you need a particular ref:
-
-```bash
-pip install 'git+https://github.com/aeresov/pytest-httpchain@main'
-```
+## Why pytest-httpchain?
 
-### Optional dependencies
+Testing HTTP APIs with plain pytest often leads to these pain points:
 
-The following optional dependencies are available:
+-   **Boilerplate accumulates** — Every test repeats the same setup: create client, set headers, make request, parse response, assert. The actual test intent gets buried.
+-   **Data threading is manual** — When one call returns a token or ID needed by the next, you end up with fragile helper functions passing state around.
+-   **Common patterns get copy-pasted** — Auth flows, base URLs, shared headers end up duplicated across test files. Fixtures might help, but they are not designed for that.
+-   **Code reviews are noisy** — The actual test logic is rarely clear because of all the boilerplate and helpers, following changes gets overwhelming quickly.
 
--   `mcp`: installs MCP server package and its starting script. Details in [MCP Server](#mcp-server).
+`pytest-httpchain` offers a more structured approach.
 
 ## Features
 
-### Pytest integration
+### Declarative JSON format
 
-Most of pytest magic can be used: markers, fixtures, other plugins.
+Test scenarios are JSON documents that describe _what_ to test, not _how_. No setup code to scroll through — the request and assertions are right there.
 
-### Declarative format
+### `$ref` with deep merging
 
-Test scenarios are written declaratively in JSON files.  
-`pytest-httpchain` supports JSONRef, so use can reuse arbitrary parts of your scenarios with `$ref` directive.  
-Properties are merged in a greedy way with type checking.
+Reuse arbitrary parts of your scenarios with JSONRef. Properties merge with type checking, so you can compose scenarios from shared fragments (auth flows, common headers, base URLs).
 
-### Multi-stage tests
+### Multi-stage execution
 
-Each test scenario contains 1+ stages; each stage is a single HTTP call.  
-`pytest-httpchain` executes stages in the order they are listed in scenario file; one stage failure stops the execution chain.
+Each scenario contains 1+ stages executed in order. One stage failure stops the chain. Use `always_run` for cleanup stages that should execute regardless.
 
-### Common data context and variable substitution
+### Common data context
 
-`pytest-httpchain` maintains key-value data storage throughout the execution.  
-This storage ("common data context") is populated with declared variables, fixtures and data saved by stages. The data remains there throughout the scenario execution.  
-Writing scenarios, you can use Jinja-style expressions like `"{{ var }}"` for JSON values. `pytest-httpchain` does variable substitution dynamically right before executing a stage, and uses common data context keys as variables in these expressions.  
-Values from common data context also might be verified during verified/asserted.
+A key-value store persists throughout scenario execution. Variables, fixtures, and saved response data all live here. Use template expressions (`{{ var }}`) anywhere in your requests — substitution happens dynamically before each stage.
 
-### User functions
+### Response processing
 
-`pytest-httpchain` can import and call regular python functions:
+-   **JMESPath** — Extract values from JSON responses directly
+-   **JSON Schema** — Validate response structure against a schema
+-   **User functions** — Call Python functions for custom extraction, verification, or [authentication](https://requests.readthedocs.io/en/latest/user/advanced/#custom-authentication)
 
--   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
+### Full pytest integration
 
-### JMESPath support
-
-`pytest-httpchain` can extract values from JSON responses using JMESPath expressions directly.
-
-### JSON schema support
-
-`pytest-httpchain` can verify JSON reponses against user-defined JSON schema.
+Markers, fixtures, parametrization, and other plugins work as expected. You're not locked into a separate ecosystem.
 
 ## Quick Start
 
@@ -95,9 +73,8 @@ def now_utc():
             }
         }
     ],
-    "stages": [
-        {
-            "name": "get_user",
+    "stages": {
+        "get_user": {
             "request": {
                 "url": "https://api.example.com/users/{{ user_id }}"
             },
@@ -116,8 +93,7 @@ def now_utc():
                 }
             ]
         },
-        {
-            "name": "update_user",
+        "update_user": {
             "fixtures": ["now_utc"],
             "request": {
                 "url": "https://api.example.com/users/{{ user_id }}",
@@ -139,15 +115,14 @@ def now_utc():
                 }
             ]
         },
-        {
-            "name": "cleanup",
+        "cleanup": {
             "always_run": true,
             "request": {
                 "url": "https://api.example.com/cleanup",
                 "method": "POST"
             }
         }
-    ]
+    }
 }
 ```
 
@@ -169,54 +144,74 @@ Scenario we created:
     finalizing call meant for graceful exit  
     `always_run` parameter means this stage will be executed regardless of errors in previous stages
 
-For detailed examples see [USAGE.md](USAGE.md).
+For detailed usage guide see the [full documentation](https://aeresov.github.io/pytest-httpchain).
+
+## Installation
+
+Install normally via package manager of your choice from PyPi:
+
+```bash
+pip install pytest-httpchain
+```
+
+or directly from Github, in case you need a particular ref:
+
+```bash
+pip install 'git+https://github.com/aeresov/pytest-httpchain@main'
+```
 
 ## Configuration
 
--   Test file discovery is based on this name pattern: `test_<name>.<suffix>.json`.  
+-   Test file discovery is based on this name pattern: `test_<name>.<suffix>.json`.
     The `suffix` is configurable as pytest ini option, default value is **http**.
--   `$ref` instructions can point to other files; absolute and relative paths are supported.  
+-   `$ref` instructions can point to other files; absolute and relative paths are supported.
     You can limit the depth of relative path traversal using `ref_parent_traversal_depth` ini option, default value is **3**.
+-   Template expressions support list/dict comprehensions. You can limit the maximum comprehension length using `max_comprehension_length` ini option, default value is **50000**.
+-   Parallel stage iterations (repeat/foreach) have a safety limit configurable via `max_parallel_iterations` ini option, default value is **10000**.
 
-## MCP Server
+## AI agent support
 
-`pytest-httpchain` includes an MCP (Model Context Protocol) server to aid AI code assistants.
+`pytest-httpchain` ships tooling to help AI coding agents (and humans) author and check test scenarios.
 
-### Installation
+### Claude Code skill
 
-The optional dependency `mcp` installs MCP server's package and `pytest-httpchain-mcp` script.  
-Use this script as call target for your MCP configuration.
+Install the authoring skill into your project (or `--global` for personal scope):
 
-Claude Code `.mcp.json` example:
+```bash
+uvx pytest-httpchain install
+```
 
-```json
-{
-    "mcpServers": {
-        "pytest-httpchain": {
-            "type": "stdio",
-            "command": "uv",
-            "args": ["run", "pytest-httpchain-mcp"],
-            "env": {}
-        }
-    }
-}
+This writes `.claude/skills/pytest-httpchain/SKILL.md` with guidance for writing scenarios.
+
+### Scenario validation
+
+Validate scenario files for structure and common problems — undefined variables, duplicate stage names, fixture/variable conflicts, stages with no assertions:
+
+```bash
+uvx pytest-httpchain validate tests/test_login.http.json
 ```
 
-### Features
+It exits non-zero when any file is invalid, so it doubles as a CI gate. The same checks also run automatically at **pytest collection time** — semantic errors fail collection and warnings are reported — so `pytest --collect-only` validates every scenario in your suite.
 
-The MCP server provides:
+### Editor schema
 
--   **Scenario validation** - validate test scenario and scan for possible problems
+A JSON Schema is published for as-you-type validation and autocomplete. Reference it from your test files:
+
+```json
+{
+    "$schema": "https://aeresov.github.io/pytest-httpchain/schema/scenario.schema.json"
+}
+```
 
 ## Documentation
 
--   [Usage Examples](USAGE.md) - Practical code examples
--   [Full Documentation](https://aeresov.github.io/pytest-httpchain) - Complete guide
+-   [Full Documentation](https://aeresov.github.io/pytest-httpchain) - Complete usage guide
 -   [Changelog](CHANGELOG.md) - Release notes
 
 ## Thanks
 
-`pytest-httpchain` was inspired by [Tavern](https://github.com/taverntesting/tavern) and [pytest-play](https://github.com/davidemoro/pytest-play).  
+This project 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_httpchain-0.2.1 → pytest_httpchain-0.3.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "pytest-httpchain"
-version = "0.2.1"
+version = "0.3.0"
 description = "pytest plugin for HTTP testing using JSON files"
 readme = "README.md"
 requires-python = ">=3.13,<4.0"
@@ -11,7 +11,9 @@ dependencies = [
     "pyrate-limiter>=3.0.0",
     "pytest-httpchain-jsonref",
     "pytest-httpchain-models",
+    "pytest-httpchain-templates",
     "pytest-order>=1.3.0",
+    "typer>=0.16.0",
 ]
 keywords = ["testing", "pytest", "requests"]
 license = "MIT"
@@ -26,9 +28,6 @@ classifiers = [
     "Topic :: Software Development :: Testing",
 ]
 
-[project.optional-dependencies]
-mcp = ["pytest-httpchain-mcp"]
-
 [dependency-groups]
 dev = [
     "flask-httpauth>=4.8.0",
@@ -52,9 +51,9 @@ default-groups = ["dev", "docs"]
 members = ["packages/*"]
 
 [tool.uv.sources]
+pytest-httpchain-core = { workspace = true }
 pytest-httpchain-jsonref = { workspace = true }
 pytest-httpchain-templates = { workspace = true }
-pytest-httpchain-mcp = { workspace = true }
 pytest-httpchain-models = { workspace = true }
 pytest-httpchain-userfunc = { workspace = true }
 
@@ -62,6 +61,9 @@ pytest-httpchain-userfunc = { workspace = true }
 requires = ["uv_build>=0.7.21,<0.8.0"]
 build-backend = "uv_build"
 
+[project.scripts]
+pytest-httpchain = "pytest_httpchain.cli:app"
+
 [project.entry-points.pytest11]
 pytest_httpchain = "pytest_httpchain.plugin"
 
@@ -97,9 +99,9 @@ pytester_example_dir = "tests/integration/examples"
 addopts = ["--log-disable=werkzeug", "--import-mode=importlib"]
 pythonpath = [
     ".",
+    "packages/pytest-httpchain-core/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",
 ]
@@ -117,9 +119,9 @@ pythonPlatform = "Linux"
 [tool.coverage.run]
 source = [
     "src",
+    "packages/pytest-httpchain-core/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",
 ]