DEPLOY & RUN
The right test version. On every bench.
Build from your code, deploy to your stations, and give operators a clear way to run it. Every result stays linked to the version that produced it.
FROM COMMIT TO COMPLETED RUN
Update the test between runs.
A new deployment can arrive while the bench is busy. The current unit finishes against the version it started with; the next run uses the update.
A new build is ready.
Commit 8f2c91a produced v1.4.2. Bench 03 is still finishing its current run on v1.4.1.
Upload when the connection returns.
A completed run goes into the local upload queue first. Try disconnecting the example station.
Keep the version with the result. Inspect the source commit, build logs and assigned stations, or re-pin a station to a previous build.
Explore deployment optionsOPERATOR EXPERIENCE
Make the next action obvious.
Scan. Run. Review.
Declare scans, instructions and phase progress with the framework. Keep each result linked to its unit and deployed version.
Explore the operator UILOCAL EXECUTION. SHARED RESULTS.
The station runs the hardware.
Separate the work that needs the bench from the work your team needs to see.
Completed runs are queued locally before upload.
when connected
Managed cloud, dedicated cloud, or self-hosted.
The local queue preserves the original run time. Receiving a new deployment and viewing shared analytics require connectivity; queued uploads resume after the connection returns.
Put one station on a known version.
Start with a procedure and the bench that already runs it.
