For us, testing is not a consulting project but a deliverable: a running test environment for your device, the test cases to go with it and the evidence that holds in an audit. After that you run it yourself – or we stay on board.
Companies that trust RX-Systems
Embedded test service
Four results, not effort
A test environment for your device
We build the test setup, wire it to your interfaces and commission it. In the end there is a running test rig on your device – not a kit you assemble yourself.
Test cases and automation
Your requirements become executable, repeatable procedures. They run automated in your CI/CD or at the bench – reproducible on every run.
Evidence to your standard
IEC 62304, IEC 61508, ISO 26262, EN 50128/50657 or DO-178C: we produce the verification evidence so that it holds in an audit – with end-to-end links between requirement, test case and result.
Handover to your team
Documentation, onboarding and training are part of it. Your team then runs the environment independently – without us.
Some customers bring us in for one project, others for every new device for years.
How it works
How a project runs
Analysis
Device under test, interfaces, standard, risk. The result is a test strategy that directs effort to where the risk sits.
Build
Hardware, wiring to your interfaces, commissioning – until the test setup runs.
Test cases and automation
Executable, repeatable, integrated into CI/CD – from requirement to dependable result.
Handover
Documentation, onboarding, training – or we stay on board for the next devices.
Standards and norms
Testing to recognised standards
We align our test strategies, processes and evidence with established standards – matched to your domain and the required safety integrity level.
ISO/IEC/IEEE 29119
The international standard for software testing: test processes, documentation and systematic test techniques as a common, verifiable foundation.
IEC 61508
The base standard for functional safety. We align verification and evidence with the required safety integrity level (SIL).
IEC 62304
The software life cycle for medical devices: structured verification and complete, audit-ready evidence for approval.
Further domain-specific standards – such as ISO 26262 (automotive), EN 50128 / EN 50657 (rail) or DO-178C (aerospace) – are addressed per project. In detail: IEC 62304 in medical technology, IEC 61508 for functional safety and the embedded testing overview.
Tools
What we work with
For Hardware-in-the-Loop we use LoopCheck, for system tests on the real device XPressRT – there test procedures start by hand and are automated step by step. Where a different tool fits better, we work with that.
Our role
We take on what isn't staffed internally
When test strategy, standards compliance and evidence aren’t staffed internally, we take that on – until your team carries it themselves. Some customers bring us in for a single device, others have us build the test environment and then take it over in full themselves.
From a running project (medical technology, IEC 62304): For a safety-critical device with a controller and FPGA backend we built the module test environments – for the QNX resource manager as well as for the FPGAs. We lead the test team, established the test strategy and test automation, and describe the test cases in Gherkin/Behave so they stay readable for non-developers. Around 2,000 specifications are checked this way, ten testers work with the environment – for four years now.
Frequently asked questions
What do I get in the end – a concept or a running environment?
A running test environment on your device: test setup, wiring, test cases and automation, plus the verification evidence to your standard. Not a concept paper, but something that tests.
Does the environment stay usable if we don't commission you again?
Yes, that is the normal case. We hand over the environment with documentation and onboarding so your team runs it independently. Whether you bring us back for the next devices is up to you.
Can I have my test environment built for me?
Yes, that is exactly our offer: we build the test environment for your device, wire it to your interfaces, write the test cases and take on the test automation – as a service, from analysis to handover.
What is risk-based testing?
Test effort is prioritised by risk: critical functions and fault cases are tested more intensively than uncritical ones. That delivers the greatest possible assurance within limited time.
Which standards do you cover?
ISO/IEC/IEEE 29119 (software testing), IEC 61508 (functional safety), IEC 62304 (medical), ISO 26262 (automotive), EN 50128/50657 (rail) and DO-178C (aerospace) – the relevant standard is agreed per project.
Do you also handle test automation?
Yes. For Hardware-in-the-Loop we use LoopCheck, for system tests on the real device XPressRT – there test procedures start by hand and are automated step by step.
Do you offer workshops and coaching?
Yes. Through hands-on workshops, training and coaching we enable your team to run the handed-over environment and efficient test processes independently in the long term.