pytest-examples
Pytest plugin for testing Python code examples in docstrings and markdown files.
pytest-examples can:
- lint code examples using
ruffandblack - run code examples
- run code examples and check print statements are inlined correctly in the code
It can also update code examples in place to format them and insert or update print statements.
Installation
pip install -U pytest-examples
Usage
Basic usage
Here's an example basic usage - lint then run examples in the foo_dir directory and the bar_file.py file.
import pytest
from pytest_examples import find_examples, CodeExample, EvalExample
@pytest.mark.parametrize('example', find_examples('foo_dir', 'bar_file.py'), ids=str)
def test_docstrings(example: CodeExample, eval_example: EvalExample):
eval_example.lint(example)
eval_example.run(example)
Check print statements
pytest-examples can also check print statements are inserted correctly.
There's the expected format of prints statemints in docstrings:
def add_two_things(a, b):
"""
```py
from my_lib import add_two_things
print(add_two_things(1, 2))
#> 3
```
"""
return a + b
And here's an example of a markdown file, again documenting add_two_things:
# How `add_two_things` works
```py
from my_lib import add_two_things
print(add_two_things(1, 2))
#> 3
```
pytest-examples can then run the code and check the print statements are correct:
import pytest
from pytest_examples import find_examples, CodeExample, EvalExample
@pytest.mark.parametrize('example', find_examples('foo_dir'), ids=str)
def test_docstrings(example: CodeExample, eval_example: EvalExample):
eval_example.run_print_check(example)
Updating files
As well as checking linting and print statements, are correct, we can also update files.
This requires the --update-examples flags AND use of the format() and run_print_update() methods.
Here's a full example of a unit test that checks code when called normally, but can update it when the flag is set:
import pytest
from pytest_examples import find_examples, CodeExample, EvalExample
@pytest.mark.parametrize('example', find_examples('README.md'), ids=str)
def test_readme(example: CodeExample, eval_example: EvalExample):
if eval_example.update_examples:
eval_example.format(example)
eval_example.run_print_update(example)
else:
eval_example.lint(example)
eval_example.run_print_check(example)
Release files for pytest-examples 0.0.18
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pytest_examples-0.0.18.tar.gz | 21.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytest_examples-0.0.18-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.4 kB
Release files / pytest_examples-0.0.18.tar.gz
| Download URL | pytest_examples-0.0.18.tar.gz |
|---|---|
| Size | 21.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a464f007f805b113677a15e2f8942ebb92d7d3eb5312e9a405d018478ec9801
|
|
BLAKE2b-256 checksum How to use checksums |
af714ae972fd95f474454aa450108ee1037830e7ba11840363e981b8d48fd16a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 6, 2025.
Transparency logRelease files / pytest_examples-0.0.18-py3-none-any.whl
| Download URL | pytest_examples-0.0.18-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86c195b98c4e55049a0df3a0a990ca89123b7280473ab57608eecc6c47bcfe9c
|
|
BLAKE2b-256 checksum How to use checksums |
09527bbfb6e987d9a8a945f22941a8da63e3529465f1b106ef0e26f5df7c780d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 May 6, 2025.
Transparency log