pytest-ipso
A pytest plugin that discovers and runs ipso notebook cell tests.
How it works
ipso stores test metadata (fixtures, patches, assertions) directly on Jupyter notebook cells. This plugin collects .ipynb files, surfaces each cell that has an ipso test as a notebook.ipynb::test name item, delegates execution to the ipso CLI, and maps the results back into pytest's reporting.
Installation
pip install pytest-ipso
ipso is installed automatically as a dependency.
Usage
pytest path/to/notebook.ipynb # run cell tests in one notebook
pytest # discover .ipynb files alongside .py tests
pytest --ipso-timeout=120 # override per-cell execution timeout (default: 60s)
Each cell test runs in its own isolated kernel, so it never affects your live notebook state.
Setting up tests
Tests are stored as cell metadata, not in the notebook source. Use the ipso CLI or an AI assistant with the ipso MCP server to create and manage them. See the ipso docs for details.
1 maintainer
Metadata
1 maintainer
Release files for pytest-ipso 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pytest_ipso-0.1.2.tar.gz | 3.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_ipso-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.5 kB
Release files / pytest_ipso-0.1.2.tar.gz
| Download URL | pytest_ipso-0.1.2.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
192658a082910df62219a764e5042be6ecbcecf610ae5010a69e99a6ff2596c8
|
|
BLAKE2b-256 checksum How to use checksums |
c8acea24e55aa0e9376922a3e1916876d657053235d757e04b11cfdfca35aa99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logRelease files / pytest_ipso-0.1.2-py3-none-any.whl
| Download URL | pytest_ipso-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b6ccefe89c5253abdf9dd71a027992c530e6ee2ca0fc07873d7b50cf74795fb
|
|
BLAKE2b-256 checksum How to use checksums |
aea38e53fd2ebc9c18613cc08e078688007bb2d48884160be77346642ded92c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logSecurity for pytest-ipso 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pytest_ipso-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
