docsteady
docsteady is a python package (and optionally Docker container) that talks to Jira and the Zephy Scale Test Management system to output Test folders and Test plans to a variety of documents by utilizing pandoc.
Quickstart
Pip install the package ::
pip install docsteady>1.2
Credentials are needed by docsteady to log into JIRA. The easiest way to do this is
by setting up the following environment variables::
export ZEPHYR_TOKEN= export JIRA_USER= export JIRA_PASSWORD=
The defaults of docsteady are to build documents based on DM defaults. The following commands are available:
generate-spec: to generate a Test Specification (baselining test cases)generate-report: for test plans and reportsgenerate-vcd: to generate the Verification Control Documentsbaseline-ve: to generate Verification Elements baseline documents.
See the docsteady documentation.
Developers
Please refer to the Developer Guide for contribution information.
Metadata
Release files for docsteady 3.1.6
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 | |
|---|---|---|---|---|
| docsteady-3.1.6.tar.gz | 1.4 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docsteady-3.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.5 MB
Release files / docsteady-3.1.6.tar.gz
| Download URL | docsteady-3.1.6.tar.gz |
|---|---|
| Size | 1.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4febe589caf7a859b821276114cb5f81e88b5b0418b3abde479859e2157a724c
|
|
BLAKE2b-256 checksum How to use checksums |
0e1bad58e307c2529faa5f68248ff28823a4fa9a4bdee7256444a92f87a1de63
|
| 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 Aug 26, 2026.
Transparency logRelease files / docsteady-3.1.6-py3-none-any.whl
| Download URL | docsteady-3.1.6-py3-none-any.whl |
|---|---|
| Size | 93.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f07d8a2cb8ebada140bf0662ad33938e3cec05f167593d87b976836b169c5c13
|
|
BLAKE2b-256 checksum How to use checksums |
e20f9790967efec7639827760f8540ec50c8c942791633effe0f5dafe40da307
|
| 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 Aug 26, 2026.
Transparency logSecurity for docsteady 3.1.6
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for docsteady-3.1.6.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 Aug 26, 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.