pypts
Hardware-oriented testing framework developed by BE-CEM-MTA.
Key Features
- YAML-based Recipes: Define test sequences, steps, parameters, and variables using structured YAML files.
- Modular Steps: Supports various step types including Python function calls, sub-sequence execution, user interaction prompts, wait times, and indexed steps for running tasks multiple times with varying inputs. Reliable order execution: Unlike pytest-order, the reliably follows the specified order.
- Variable Scopes: Manages global variables for the recipe and local variables within sequences.
- Threaded Execution: Runs recipes in a separate thread using
pts.run_pts. - Incremental Reporting: Generates a detailed CSV report (
report.csv) in real-time as steps complete. - Contextual Reports: Includes run context (Recipe Name, File Name, Serial Number) and step context (Sequence Name) in reports.
- HTML Reports: Provides a utility to convert the CSV report into a styled HTML file (
report.html) for easy viewing, similar topytest-html. - Event System: Uses queues for inter-thread communication and event reporting (e.g., step start/end).
For full documentation, please visit PTS Framework Documentation.
=======
Continuous integration and releases
The project is tested in a disposable Python 3.13 Docker image. To reproduce the GitHub CI build locally, run:
docker build --build-arg SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PTS_FRAMEWORK=0+local -t pts-framework-ci .
docker run --rm pts-framework-ci
Creating a protected vX.Y.Z tag runs the same tests, builds the wheel and source
distribution, and publishes them to TestPyPI. Verify the TestPyPI package in a clean
environment before approving the pypi GitHub Environment:
python -m pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ pts-framework==X.Y.Z
Approval publishes the same distributions to PyPI. GitHub retains the release artifact for 30 days; PyPI is the permanent package source. See release configuration for the one-time setup.
Licences
pypts is distributed under the LGPL-2.1-or-later licence.
pypts comes with a dependency licence compatibility analysis report.
Metadata
Release files for pts-framework 0.6.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 | |
|---|---|---|---|
| pts_framework-0.6.2.tar.gz | 106.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pts_framework-0.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 240.5 kB
Release files / pts_framework-0.6.2.tar.gz
| Download URL | pts_framework-0.6.2.tar.gz |
|---|---|
| Size | 106.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8af2e42bec4a7c641bc4ef3149bcc4975c7b200028479629867a082069e36d76
|
|
BLAKE2b-256 checksum How to use checksums |
4b13b516c2f751f5c18e306800129c927a38f47ab80f7217da52564c0634fb9d
|
| 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 3, 2026.
Transparency logRelease files / pts_framework-0.6.2-py3-none-any.whl
| Download URL | pts_framework-0.6.2-py3-none-any.whl |
|---|---|
| Size | 133.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1cd0e99cc49366e4f2ea36d8dbfed01ab438bb9a2e56ef1a8b5663e2b5c66b4b
|
|
BLAKE2b-256 checksum How to use checksums |
37d39a3d68b878e43d9e54058d1c406d60f39742746c4f915c67afad9b1966f5
|
| 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 3, 2026.
Transparency log