Embedded software testing checks whether a device’s firmware does exactly what it should – reproducibly and verifiably. Testing embedded systems ranges from the isolated component to the finished device. We take on the build, the automation and the evidence – you test from day one.
Overview
From module test to production test
Test environments & test automation
We build the test environment for your device, write the test cases and take on the embedded test automation – as a service, until your team carries it themselves.
Hardware-in-the-Loop (LoopCheck)
HIL test system for embedded firmware: your controller runs against a simulated environment – reproducibly, with deliberate fault injection, tests in C, C++ or Python.
System test on the real device (XPressRT)
System test, verification, acceptance and end-of-line on the finished device – starting manually, automated step by step, an audit-ready record per unit.
Medical technology (IEC 62304)
Verification of medical device software for IEC 62304 – black-box system tests and evidence on the real device, without a real patient device.
Functional safety (IEC 61508)
Verification of safety-related software for IEC 61508 with SIL evidence – delivered up to SIL 3 in real projects.
Frequently asked questions about embedded testing
What is embedded software testing?
Testing the firmware of an embedded device against its requirements – from module tests of individual components through software- and hardware-in-the-loop to a system test on the finished device. The goal is reproducible, verifiable proof that the software works correctly.
Which test levels do you cover?
Module test, software-in-the-loop (SIL), hardware-in-the-loop (HIL) and black-box system test on the real device – through to end-of-line testing in production.
How do you test embedded systems reproducibly?
Through an automated test environment: the firmware runs against simulated or real signals, and results are checked identically against limits on every run – integrated into CI/CD and with end-to-end evidence.
To which standards do you produce evidence?
IEC 62304 (medical), IEC 61508 (functional safety), ISO 26262 (automotive), EN 50128/50657 (rail), DO-178C (aerospace) and ISO/IEC/IEEE 29119 – the relevant standard is agreed per project.