Skip to content
Infuse-HTF · Hardware Test Framework

From test code to a line you can trust.

A purpose-built test-jig control plane for ultra-low-power IoT. Build programming, provisioning and checks once. Keep every station current. Know what happened to every unit.
Open Infuse-HTFRead the HTF docsTalk about production test
Infuse-HTF station dashboard: tests run, success rate, average duration and daily test outcomes
Infuse-HTF (Hardware Test Framework) is a control plane for hardware test stations (test jigs). You build the test once; HTF keeps the stations current and makes every unit’s result visible.

Why it exists

Writing the first test is easy. The hard part is keeping every station aligned as the product changes, then understanding a fail without chasing files on the floor.

What it does

Stations run next to the device. HTF is the control plane:
  1. 1
    Describe the sequence in code (erase → validation firmware → provision → checks → release firmware → keep the evidence).
  2. 2
    Push the right test version and firmware to the station.
  3. 3
    The jig stays focused on the hardware.
  4. 4
    Health, stage, results and logs come back to one place.
  5. 5
    A fail is tied to station, stage, device and diagnostics.

Multiple lanes on one jig are tracked.

Infuse-HTF kiosk view: enter a DUT ID to start a test, with each stage and its console output
The station kiosk: scan or enter a DUT ID, then watch each stage run.

Any jig, any hardware

Infuse-HTF is not tied to Infuse. Use it with any test-jig hardware and any firmware: it versions the test, keeps every station current and records every result, whatever you are building.

Each station runs embeint-htf-station, the extensible Python runtime for HTF stations. Install it on the station machine and extend it for your jig. It needs Python 3.14 or later.

embeint-htf-station on PyPISource on GitHub
Station machine
pip install embeint-htf-station

Infuse

On Infuse, HTF goes further: it can pull per-device provisioning data, write it on the jig, run Infuse validation, and keep the evidence before release firmware is flashed. Units leave the line provisioned and checked — not “probably fine.”
Infuse-HTF run log: passed stages and the full console output for one device under test
Every run keeps its stages and console output.

Who it is for

Teams leaving bench-tape-and-hope. First commercial run through a manufacturer-run line. Firmware, identity, connectivity or quality have to be right before the box ships.

What we are not saying

HTF is not a fleet-management product and not a generic analytics suite. It is the loop from versioned test + firmware + Infuse provisioning to the live station and the evidence.
“You shouldn’t need four vendors and a year to get a sensible architecture.”
Karl Von Richter

Karl Von Richter

Co-founder · CTO

Talk about production test.

Book a 15-min discovery callOpen Infuse-HTF