respan-instrumentation-pytest
An opt-in pytest plugin that records one workflow for each native session and one task across each test's setup, call and teardown. Native application spans remain nested under their test. The plugin supports current pytest 9.1.1 and the declared 7.4.0 floor, async tests with pytest-asyncio, and independent xdist worker trees.
pip install respan-instrumentation-pytest
pytest --respan-tracing
The pytest11 entry point is explicit. Enable with RESPAN_PYTEST_ENABLED=true or respan_tracing = true in pytest.ini. Optional RESPAN_PYTEST_WORKFLOW_NAME / respan_workflow_name names the session. The plugin uses an existing released OTel provider when available; otherwise released RespanTelemetry configures export from RESPAN_API_KEY and optional RESPAN_BASE_URL.
The actual finalized reports supply pass, skip, xfail, XPASS, strict XPASS failures, phase durations and exit codes. Native collection errors and interruption keep their original outcomes. Failed spans use OTel error status and native exception types; permitted failure messages are redacted. HTTP status, model usage and failure-as-output are never invented. Stored backend status and payload projection are separate acceptance checks.
Content controls
--no-respan-capture-content, RESPAN_PYTEST_CAPTURE_CONTENT=false, TRACELOOP_TRACE_CONTENT=false, RESPAN_TRACE_CONTENT=false, or the canonical content-disabled OTel context omit input/output and failure messages. Initial bounds cannot widen. Ambient and supplied suppression, observed finished ancestors, unknown local parents, and context exit before span end are checked. Parameter IDs are stripped from structural names/paths; outcome and phase summaries remain visible. Fixture return values are never inspected.
Permitted builtin JSON parameters retain full arrays, false/zero, and strings. Credential values are redacted; schema field names remain with sensitive defaults redacted. Unknown custom conversion hooks and iterators are not called. An explicit max_attribute_chars requests a JSON truncation summary; the default keeps complete known JSON.
Observer faults preserve native pytest exits and clean up owned contexts. Activation/deactivation is idempotent, retains foreign plugins/processors and does not reset the shared Respan tracer singleton. The companion examples run locally by default and cover the same behaviors using the released dependencies.
Metadata
Release files for respan-instrumentation-pytest 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 |
|---|---|---|---|---|
| respan_instrumentation_pytest-0.2.0.tar.gz | 10.4 kB | With provenance | Details for respan_instrumentation_pytest-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| respan_instrumentation_pytest-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for respan_instrumentation_pytest-0.2.0-py3-none-any.whl |
Total release size: 23.4 kB
Release files / respan_instrumentation_pytest-0.2.0.tar.gz
| Download URL | respan_instrumentation_pytest-0.2.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
049a5f6bbd31a6bded3212e5ab168059426721ed5595bffddfc6b58fb0e6cd90
|
|
BLAKE2b-256 checksum How to use checksums |
6e0a4b074a3661529e744b71882acade982da823089031c7ee2323a7cecbc4f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logRelease files / respan_instrumentation_pytest-0.2.0-py3-none-any.whl
| Download URL | respan_instrumentation_pytest-0.2.0-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fffd60ea4de1d82a449992d37e186bc7d2c8c0104ecb47e2ed1c9d8a31382f72
|
|
BLAKE2b-256 checksum How to use checksums |
c246470f3f3f16a40ec84d934b6a499f7daf63a4a074198d94d4ee592f0549a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 13, 2026.
Transparency logSecurity for respan-instrumentation-pytest 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 respan_instrumentation_pytest-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 Oct 13, 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.