dirigent-testing
Test doubles and pytest fixtures for writing and testing dirigent blocks.
Installing it registers the fixtures by entry point, so a block author writes no conftest.
block_ctx is a step context with a recording log and real storage behind it, and
call_block validates a config the way the engine does before making the block's first call.
check_pack_examples checks a pack's own example documents against its own Contribution
-- format, code, blocks, config schemas, and the connections a step names, which the
document may either carry or list under requires.connections -- without importing
dirigent-core, and assert_contribution_conforms checks the blocks a contribution provides
are well-formed. Both return a list of human-readable issues; an empty list means it passed.
1 maintainer
Metadata
1 maintainer
Release files for dirigent-testing 0.36.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 |
|---|---|---|---|---|
| dirigent_testing-0.36.0.tar.gz | 18.2 kB | With provenance | Details for dirigent_testing-0.36.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirigent_testing-0.36.0-py3-none-any.whl | Python 3 | none | any | Details for dirigent_testing-0.36.0-py3-none-any.whl |
Total release size: 40.0 kB
Release files / dirigent_testing-0.36.0.tar.gz
| Download URL | dirigent_testing-0.36.0.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51df34bc1c32c2a6baf13feef38f6ef70791f4a6173da38dc6d6a41a4d572261
|
|
BLAKE2b-256 checksum How to use checksums |
2fab97ea77d4cb8a5a3f7af42aa7b3a5a8fcae79289c2c5a96b4cd89a7b3dda6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 4, 2026.
Transparency logRelease files / dirigent_testing-0.36.0-py3-none-any.whl
| Download URL | dirigent_testing-0.36.0-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c4e94267ad4a80ab0b211c2aa28e07ad7dc7510156e788ded4163b87375e885
|
|
BLAKE2b-256 checksum How to use checksums |
de9cb80a3d4898a64700aba0000c9c12ff6444c9653eefba95439099a2cc98c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 4, 2026.
Transparency logSecurity for dirigent-testing 0.36.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 dirigent_testing-0.36.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 Nov 4, 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.
