Convert a Postman Collection v2.1 JSON file into a runnable pytest test suite using the postman2pytest CLI. Use when the user has a Postman collection (a .postman_collection.json or v2.1 JSON export) and wants to run it as pytest in CI, when migrating from Postman/Newman to a Python-native test stack, when bridging Postman-documented APIs into a pytest-based regression suite, when the user asks to generate pytest tests from Postman, or when the user mentions wanting to keep Postman as the source of truth but run the suite with pytest.
93
100%
Does it follow best practices?
Impact
100%
1.00xAverage score across 2 eval scenarios
Passed
No known issues
Thank you for your interest in contributing!
git clone https://github.com/golikovichev/postman2pytest
cd postman2pytest
python -m venv .venv
source .venv/bin/activate # Windows: .venv\Scripts\activate
pip install -e ".[dev]"
pip install pytestpytest tests/ -v --tb=shortAll tests must pass before opening a PR.
core/
parser.py - Postman JSON → ParsedRequest objects
generator.py - ParsedRequest list → pytest file via Jinja2
templates/
test_collection.jinja2 - output template
tests/
test_parser.py - unit tests for parser
test_generator.py - unit tests for generator
main.py - CLI entry point
data/ - sample collections for manual testinggit checkout -b feat/my-changepytest tests/ -v passespydantic, jinja2, requestscore/parser.py free of business logic unrelated to parsingcore/generator.py thin - logic belongs in the template or the model.tessl-plugin
evals
scenario-1
scenario-2