This release is a pre-release and may not be stable for production use.
pyplines-test
Test deployed Pyplines through the public API. Authentication and connection
selection use the session saved by pyplines auth login, or the standard
PYPLINES_SERVER_URL, PYPLINES_WORKSPACE, and PYPLINES_ACCESS_TOKEN variables.
Explicit global --server and --workspace flags override saved settings.
pyplines-test version
pyplines-test run tests/hello-world.yaml
pyplines-test run tests/ --report results.json
AUTOMATION_MODE=enabled pyplines-test run tests/hello-world.yaml
Cases target existing, ready Pyplines. They do not build or deploy resources. All selected cases are preflighted before execution. Test workloads have real side effects: only use suitable Actions. Load/stress concurrency is outstanding Runs, not requests per second. Interruptions/timeouts do not cancel remote Runs.
See examples/v1alpha1/tests and specification 0310 for the canonical documents
and report semantics. Place only cases you intend to execute in a selected directory.
Reports contain versions, immutable identities, timing and outcome codes—not inputs, output values, logs or credentials. Server/executor identities are a preflight snapshot; unavailable executor metadata remains explicit. This is not per-Run binary attestation. Action image digests identify executable content; SDK/Python versions cannot be inferred from an Action version alone.
Targets include executionConfiguration when the server supplies it: preflight
Workspace settings version, size map and Workspace/installation aggregate limits.
Each observed Run also contributes its immutable spec.execution allocation
snapshot to the sample. These distinguish policy from captured allocations; a
preflight policy snapshot does not prove which aggregate limits were used later.
Development: uv run --project apps/test pytest -q apps/test/tests.
Live installed-wheel smoke:
python3 tooling/qualification/qualify-v1alpha1-client.py --docker --test-tool-only.
Worker connections are reused; concurrency is bounded without CLI subprocesses
or Run-state polling. End-to-end measurements still include network/observation
cost and are not equivalent to Action execution duration.
PyPI publication requires a trusted publisher for pyplines-test, workflow
publish-release.yml, environment pypi, just like the other packages.
1 maintainer
Metadata
1 maintainer
Release files for pyplines-test 2026.9.14a1
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 |
|---|---|---|---|---|
| pyplines_test-2026.9.14a1.tar.gz | 78.7 kB | With provenance | Details for pyplines_test-2026.9.14a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyplines_test-2026.9.14a1-py3-none-any.whl | Python 3 | none | any | Details for pyplines_test-2026.9.14a1-py3-none-any.whl |
Total release size: 89.1 kB
Release files / pyplines_test-2026.9.14a1.tar.gz
| Download URL | pyplines_test-2026.9.14a1.tar.gz |
|---|---|
| Size | 78.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b1a9030a1c784faf954a57f9292a60fca8d58566e6a2be8464aec575a467a1d
|
|
BLAKE2b-256 checksum How to use checksums |
ba1365e3695efb2d7a81be97bf3a44c8941382a7c2e566a3160b6cb170a72598
|
| 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 Sep 15, 2026.
Transparency logRelease files / pyplines_test-2026.9.14a1-py3-none-any.whl
| Download URL | pyplines_test-2026.9.14a1-py3-none-any.whl |
|---|---|
| Size | 10.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00bfa63c2700d140831c3b9644dba1b0238d4e386f2cd964ad15ee6e6c72696f
|
|
BLAKE2b-256 checksum How to use checksums |
39cf937ee6d6309d98c6904cf935df49a6149a4628fc9a0096c10519f442f604
|
| 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 Sep 15, 2026.
Transparency logSecurity for pyplines-test 2026.9.14a1
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 pyplines_test-2026.9.14a1.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 Sep 15, 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.
