Integration #

Litmus is built for incremental adoption. Start where the existing pain is, expand from there. Each path below is independent — you don't have to migrate everything at once. Same category axis as the rest of the docs (concepts, how-to, reference).

Runtime #

Bring existing test code, runners, or hardware under Litmus's runtime — adopt an existing pytest suite, drive Litmus from a non-pytest runner, plug in your own instrument drivers. Mirrors reference/runtime on the other axis.

• Existing pytest projects — adopt Litmus from a working pytest suite
• Harness — the imperative TestHarness API for non-pytest runners (OpenHTF bridges, hand-written loops)
• Instruments — bring your own drivers (PyVISA / PyMeasure / vendor SDKs)

Data #

Get Litmus's data into external systems — warehouse imports, dashboards, log streams, results submission from non-pytest sources.

• Results API — LitmusClient for submitting runs from any language
• Logging — patterns for capturing measurements alongside existing test code; bridging to Python's logging, syncing to external databases, sealing runs to cloud storage
• Grafana — pgwire data source plus ten shipped dashboards
• Lakehouse import — pull Litmus parquet runs into your warehouse