zephyr-scale-test-cycle
Update Zephyr Scale Cloud test cycle executions from CI, workflows, or BDD.
Install
pip install zephyr-scale-test-cycle
Requires Python 3.10+.
CLI
After install, use a console script (both names call the same CLI), or the module form:
zephyr_scale_test_cycle --test-cycle-id R123 --testcase-id T456 --status Pass
zephyr-scale-cycle-update --test-cycle-id R123 --testcase-id T456 --status Pass
python -m zephyr_scale_test_cycle --test-cycle-id R123 --testcase-id T456 --status Pass
Common options:
--version— Print the program version and exit.--project-key— Jira project key when ids are short (default:ZEPHYR_PROJECT_KEYenv).--duration— Execution duration in seconds.--comment— Execution comment.--environment— OptionalenvironmentNamefor Zephyr.--no-create-execution— Do not POST a new execution if the testcase is missing from the cycle.
Environment variables
| Variable | Required | Description |
|---|---|---|
ZEPHYR_SCALE_TOKEN |
Yes (for API calls) | Zephyr Scale Cloud API bearer token. If unset or empty, requests run without a valid token and the API will fail. |
ZEPHYR_PROJECT_KEY |
When using short cycle ids | Jira / project key (e.g. PROJ). Needed when --test-cycle-id is only the numeric part (e.g. R123) instead of a full key like PROJ-R123. Same as passing --project-key. |
ZEPHYR_SCALE_BASE_URL |
No | API root URL. Default: https://api.zephyrscale.smartbear.com/v2. Override for custom endpoints or testing. |
Example:
export ZEPHYR_SCALE_TOKEN="your-api-token"
export ZEPHYR_PROJECT_KEY="PROJ"
zephyr-scale-cycle-update --test-cycle-id R123 --testcase-id T456 --status Pass
Library
from zephyr_scale_test_cycle import update_test_execution, get_execution_keys
ok = update_test_execution(
test_cycle_id="PROJ-R123",
testcase_id="PROJ-T456",
status="Pass",
)
License
Proprietary — see LICENSE.
Metadata
Release files for zephyr-scale-test-cycle 0.1.2
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 | |
|---|---|---|---|---|
| zephyr_scale_test_cycle-0.1.2.tar.gz | 7.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zephyr_scale_test_cycle-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.9 kB
Release files / zephyr_scale_test_cycle-0.1.2.tar.gz
| Download URL | zephyr_scale_test_cycle-0.1.2.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
409b2570b0e38f5314e76e59b8e4192bec1e83337af06b13b85f164d16305da5
|
|
BLAKE2b-256 checksum How to use checksums |
4827ca37ac57b0068e372826c459bcac6c0b251e6e8a97da9376c4fd9cad4c02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / zephyr_scale_test_cycle-0.1.2-py3-none-any.whl
| Download URL | zephyr_scale_test_cycle-0.1.2-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4a428d2f2d2c9232b27e804a6190471163651f8b4a6f7d6cdbd1ea6e3e1f48fa
|
|
BLAKE2b-256 checksum How to use checksums |
6405eaf699c61665bbeb84138870be91f13b70464f32024d752589ea0601372a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for zephyr-scale-test-cycle 0.1.2
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.