Workflow Integration¶

LoopCheck integrates naturally into your development workflows.

Local testing
Continuous integration
Automated regression
Nightly builds

Example: Custom Test Setup for a MedTech Company¶

Real LoopCheck test setup: device under test wired to the LoopCheck board

A real bench setup: the customer's device under test (left) connected through the hardware interfaces to the LoopCheck board (right).

flowchart LR
    DUT["Device under Test<br/><i>Customer's own Firmware</i>"]
    HWI["Hardware Interfaces"]
    BOARD["LoopCheck Board"]
    RT["LoopCheck Runtime"]
    TEST["Test Logic<br/>(C / C++ / Python)"]
    CI["CI/CD Pipeline"]
    OUT["Automation, Logging<br/>& Test Results"]

    DUT <--> HWI
    HWI <--> BOARD
    BOARD <--> RT
    RT <--> TEST
    CI --> RT
    RT --> OUT

The device under test runs the customer's own firmware. It is connected through the hardware interfaces to the LoopCheck board, which is driven by the LoopCheck runtime. Test logic written in C, C++ or Python executes against that runtime — either locally or triggered from the CI/CD pipeline — and produces automation, logging and test results.

What this looks like for engineers

Technical detail: cores, protocols and timing