The typical workflow is:
* Several clients,
usually running on different platforms/configurations,
monitor periodically for updates
at the project version control system (VCS).
* When a client detects any changes, it starts an execution.
* Execution progress and results are reported to the TestFarm server.
* The server collects such data into a public web site.
* Developers can take a look at that web site to see whether
their changes had unexpected impacts over other platforms or configurations.
Metadata
Release files for testfarm 2.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 |
|---|---|---|---|---|
| testfarm-2.0.tar.gz | 50.9 kB | Without provenance | Details for testfarm-2.0.tar.gz |
Release files / testfarm-2.0.tar.gz
| Download URL | testfarm-2.0.tar.gz |
|---|---|
| Size | 50.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1c34e70713f3a51069e54962e06c5327ed2e161242094cc158bebf6ff3a04192
|
|
BLAKE2b-256 checksum How to use checksums |
7efa288e8919b328b57576ea4112140c0e4c7998eb04ddd5fa3d7fcb33cda17e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for testfarm 2.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.