messagefoundry-harness
The standalone test harness for MessageFoundry — the open-source healthcare integration engine (HL7 v2.x and more). This package is synthetic-only tooling to exercise a running engine: an interactive send/receive (MLLP) GUI, a headless load engine (rate/concurrency profiles, latency + throughput, drain / no-loss checks), and a two-node failover-under-load harness for the clustered SQL Server / PostgreSQL store.
Published in lockstep with the engine — install the version that matches your
messagefoundry. All traffic is synthetic, PHI-free generators. This is a test/ops tool, not part of the engine runtime — themessagefoundryengine wheel does not contain it.
Install
pip install "messagefoundry-harness==<version>" # pulls messagefoundry[harness] (engine + API client + PySide6)
Use
python -m harness # send/receive/compose/monitor GUI
python -m harness --list-profiles # list built-in load profiles
python -m harness --load reference --engine https://127.0.0.1:8765 --cacert <engine-data-dir>/api-generated-cert.pem --token <T> # headless load run
python -m harness --failover failover --db-backend sqlserver # two-node SIGKILL-under-load
See the load-testing guide
and the harness/ sources in the repo for details.
Metadata
Release files for messagefoundry-harness 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| messagefoundry_harness-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / messagefoundry_harness-0.5.1-py3-none-any.whl
| Download URL | messagefoundry_harness-0.5.1-py3-none-any.whl |
|---|---|
| Size | 616.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7a0d5d620a2d20db0681f91802d71015242fb160b0fea58dfa77ac74c4c87c3
|
|
BLAKE2b-256 checksum How to use checksums |
e330ad57151bbcc4644ae3b68151b7e11b0407941883039ea541fd803a4cec8a
|
| 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 Oct 1, 2026.
Transparency log