Connected test systems

The problem

A test result needs context. Which device was tested? What happened on the latest run? Does a failure still need attention? Capturing those details makes a test setup more useful than a pass or fail indicator alone.

Connecting the workbench

My test-jig work connects physical testing with Bench, the results app in Cabel Workspace. Bench organises reported runs and helps surface unresolved failures alongside the other work on the dashboard.

A later passing run can resolve an earlier failure for the same jig and device serial. Errors and aborted runs remain visible rather than disappearing from the picture of how the system is performing.

The software around the hardware

The integration focuses on retaining useful context and making the next action accessible. Test failures can lead to follow-up tasks, while jig activity helps identify equipment that may need attention.

This project brings together device-side behaviour, result reporting, database records, and the interface used to review them.

Current outcome

This is an ongoing personal engineering project. These notes describe the connected testing workflow; they do not claim certified test coverage or production qualification.

What this demonstrates

• Connecting physical systems with software tools.
• Treating errors and interrupted tests as meaningful outcomes.
• Turning test information into follow-up engineering work.
• Considering how a system will be operated as well as how it is built.