pytest-collect-markers
A pytest plugin that collects test markers and outputs them to a JSON file.
Installation
pip install pytest-collect-markers
Usage
Run pytest with the --collect-markers flag to collect all markers from your tests:
pytest --collect-markers
This will create a markers.json file containing a mapping of test node IDs to their markers.
Options
| Option | Default | Description |
|---|---|---|
--collect-markers |
False |
Enable marker collection |
--markers-output |
markers.json |
Output file path for collected markers |
Example
pytest --collect-markers --markers-output=my-markers.json
Output Format
The output JSON file maps test node IDs to their list of markers:
{
"tests/test_example.py::test_slow_operation": ["slow", "integration"],
"tests/test_example.py::test_fast_unit": ["unit"]
}
Development
# Install with uv
uv sync
# Run tests
uv run pytest
License
MIT
Metadata
Release files for pytest-collect-markers 0.2.0
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 | Actions |
|---|---|---|---|---|
| pytest_collect_markers-0.2.0.tar.gz | 1.5 kB | With provenance | Details for pytest_collect_markers-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_collect_markers-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for pytest_collect_markers-0.2.0-py3-none-any.whl |
Total release size: 4.3 kB
Release files / pytest_collect_markers-0.2.0.tar.gz
| Download URL | pytest_collect_markers-0.2.0.tar.gz |
|---|---|
| Size | 1.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e945c78136054cca8d1eb92902bf82963fbc36991df48d59ab3240b781ef487
|
|
BLAKE2b-256 checksum How to use checksums |
c776e5d616143ee568357f68c4c86669375afbff927469505ac53e3ce4dd1c7e
|
| 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 Jan 24, 2026.
Transparency logRelease files / pytest_collect_markers-0.2.0-py3-none-any.whl
| Download URL | pytest_collect_markers-0.2.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68789261ae7861c228961145ddd23a65843e66a80ba5a110fde13012781ab18e
|
|
BLAKE2b-256 checksum How to use checksums |
3d0a5d91ff6221e7f8c69ef1670335f48dc3b02610ce655222d28fd4b149bd05
|
| 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 Jan 24, 2026.
Transparency logSecurity for pytest-collect-markers 0.2.0
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
Both files in this release have been uploaded with provenance metadata.
Attestation for pytest_collect_markers-0.2.0.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 Jan 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.