Sharedincc Test Fabric Journey Reporter for Python
Zero-runtime-dependency Python reporter for the canonical Test Fabric backend-journey event and result protocols.
from sharedincc_test_fabric_journey import JourneyReporter
reporter = JourneyReporter(
run_id="run-one",
project_id="example-project",
journey_id="password-reset",
journey_version=1,
attempt_id="attempt-one",
attempt_ordinal=1,
)
reporter.action_started("request-reset", "Request password reset.")
reporter.assertion(
assertion_id="single-use-token",
description="A reset token can be consumed only once.",
semantic_class="replay-resistance",
authority="mandatory",
result="passed",
expected_summary="A second use is rejected.",
observed_summary="The second use returned the consumer-owned rejection.",
evidence_refs=["reset-proof"],
)
reporter.finish(status="passed", stability="stable", required_evidence_refs=["reset-proof"])
The reporter writes one canonical JSON object per line. Consumer assertions, fixtures, commands, and business meaning remain consumer-owned.
The optional pytest plugin exposes test_fabric_journey_reporter. Configure identity through pytest markers or environment variables documented in the package API. Native Python commands remain independently runnable.
Metadata
Release files for sharedincc-test-fabric-journey 1.3.1
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 |
|---|---|---|---|---|
| sharedincc_test_fabric_journey-1.3.1.tar.gz | 8.8 kB | Without provenance | Details for sharedincc_test_fabric_journey-1.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sharedincc_test_fabric_journey-1.3.1-py3-none-any.whl | Python 3 | none | any | Details for sharedincc_test_fabric_journey-1.3.1-py3-none-any.whl |
Total release size: 17.1 kB
Security for sharedincc-test-fabric-journey 1.3.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.