ub-test-reports
A tool for the sphinx-needs family – not a Sphinx extension, and nothing to add to conf.py.
It turns test results into needs without running Sphinx, and holds everything about test reports that does not need a documentation build:
the parsers – JUnit XML (pytest, googletest, ctest, nose and friends) and tox-envreport style JSON;
the result vocabulary – one spelling for every outcome, whichever report it came from;
deterministic case IDs – the same case gets the same need ID in every run;
the [test_reports] model of ubproject.toml, read through ub-project;
the converter – the test-reports build needs command, which writes a needs.json that sphinx-needs can import;
the pytest plugin – -p ub_test_reports.pytest_plugin, which shapes the JUnit XML pytest writes (source locations, per-case properties for traceability).
Install the converter with:
pip install ub-test-reports
and the pytest plugin with:
pip install "ub-test-reports[pytest]"
To show the same reports inside a Sphinx documentation build, install the extension, sphinx-test-reports, which depends on this package.
Documentation: the “Without Sphinx” section of https://sphinx-test-reports.readthedocs.io/en/latest/
Metadata
Release files for ub-test-reports 2.0.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 |
|---|---|---|---|---|
| ub_test_reports-2.0.0.tar.gz | 50.7 kB | Without provenance | Details for ub_test_reports-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ub_test_reports-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for ub_test_reports-2.0.0-py3-none-any.whl |
Total release size: 107.9 kB
Release files / ub_test_reports-2.0.0.tar.gz
| Download URL | ub_test_reports-2.0.0.tar.gz |
|---|---|
| Size | 50.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
97615c65af1f8c0e254b0798090a58ea5bbc072138b8ff3e9f06d7e24c217a8d
|
|
BLAKE2b-256 checksum How to use checksums |
94a0da4cf9e769836d27003b4d5cd32c163cee49a8646de0c1f90e03624ffb8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / ub_test_reports-2.0.0-py3-none-any.whl
| Download URL | ub_test_reports-2.0.0-py3-none-any.whl |
|---|---|
| Size | 57.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f149cb7802e67e0d3d483ed6a8788e8c582088c7cdb90e58ddcfbb2ad6fc53fc
|
|
BLAKE2b-256 checksum How to use checksums |
0c0e8dafac25869a88c23f65e3a96f5acee772f61bb7801e858bb7ba9db3fd93
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for ub-test-reports 2.0.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.
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.