Services · Verification
Systematic testing.
We test electronics and software against their requirements, from unit tests and HiL setups to EMC measurement. That is where safety and reliability come from.
What we stand for
We test against the product's requirements
Repeatability
A result only becomes evidence when the same setup produces the same result. That is why test cases, test setup and tool versions are defined in a traceable way.
Test depth follows the safety level
The depth of testing usually depends on the applicable regulations. Budgets for different test depths can be estimated as early as the planning stage.
Qualified test tools
For safety-related projects IEC 61508 calls for evidence that the test tool itself is fit for purpose. We keep that evidence up to date for all our tools.
The most economical test level
A fault found by a unit test costs a fraction of what the same fault costs in the HiL setup or at the test lab. We run every test at the level where it is cheapest.
- IEC 61508
- ISO 13849
- IEC 62304
- MDR
- IEC 61000
What we test
Unit and integration tests
Automated in the pipeline, on every commit. SiL tests in a simulated environment and HiL tests on the target hardware.
Hardware bring-up
We fully bring up prototypes and measure them.
System test
The complete device is tested against its specification. Ideally both in-house and at your site.
EMC, ESD and climate
Emissions, immunity, temperature and humidity. Pre-compliance measurements in-house, approval measurements in an accredited laboratory.
Regression testing throughout the service life
The Cyber Resilience Act calls for the product's security to be tested regularly and effectively throughout the support period. That is why the test cases run against every new version, even years after release.
Test station for series production
At the end of the production line, the device is programmed and tested. qdTest provides a ready-made system for this.
A product is good when the customer comes back, and the device does not.
Your benefits at a glance
Faults surface early
Pre-compliance measurements reveal problems while the layout is still open. An EMC finding on the finished device costs a redesign.
A shorter approval phase
If you arrive at the accredited laboratory with pre-measured assemblies, you are less likely to need a second appointment.
We stand behind the test approach
We explain to the certification body why the chosen test depth is sufficient for your safety level. You do not have to have that discussion on your own.
The test setup belongs to you
Test cases, scripts and the description of the setup are handed over too. You can continue the testing yourself or leave it with us.
From test planning to series production
On request as a fixed-price contract.
Test planning
For every requirement, we define how it will be verified: analysis, test, inspection or measurement. This results in the test plans.
Test cases and setup
The test cases are written and released; the test equipment is built or procured.
Pre-compliance
First measurements on the prototype, while circuit and layout can still be changed. Changes at this point usually do not put milestones at risk.
Verification
The planned tests are carried out, automated wherever possible.
Approval testing
The final measurements take place in an accredited laboratory. We prepare the device under test, attend the appointment and handle any rework.
Production testing
The end-of-line test station goes into operation.
Build on our foundation
Production testViewqdTest
Programming and testing at the end of the production line. Configured for your device and delivered ready to run, so you do not need to build your own test station.
View
Transparency from the start
Do you also test devices we developed ourselves?
Yes. We need the requirements, the schematic and the interface description. If there is no testable set of requirements, we create one first.
Do you measure yourselves or in a laboratory?
Both. We carry out in-house the pre-compliance measurements we can do ourselves, and the rest at partner laboratories where we get quick access. The approval measurements then take place in an accredited laboratory.
What is the difference between verification and validation?
Verification checks whether the device was built correctly against its specification. Validation checks whether the specification asked for the right thing. We support both.
Where is the testing done?
In Offenburg, and nowhere else. We work with our own people. Whoever tests your device sits in the same building as the people who develop the electronics and the firmware.
Do you work with AI?
Yes, systematically. Anything a tool contributes goes through the same checks as any other work: review, cross-check, test. We build our AI system ourselves, so we know what it does, and we keep improving it.
Tell us about your next project.
Tell us about your product and your schedule. We will tell you how we would approach the project and whether we see any major risks. The assessment, up to an indicative price, is free of charge.
