Product · Off-board · Test automation
Dolphin
Automated software verification and test automation. Dolphin closes the loop between what was specified and what actually runs: it plugs into CI chains and drives diagnostic test scenarios against virtual and real ECUs, so the same cases run in the pipeline and on the rig.
3 days → 1 hrelease build, every test case automatedEvery commit
Module-level CI. Built and tested automatically.
System-level CI. Integrated and tested again.
Dolphin runs the same test cases — UDS services, fault codes, security access, software download.
In the pipeline
Virtual ECUs. Fast, on every change.
On the rig
Real ECUs. On the HIL rig, with external equipment driven through its API.
Capabilities
What Dolphin does.
In a software-defined vehicle any change can quietly break a diagnostic. Dolphin turns verification from the slowest manual step into an automatic one.
- 01
Diagnostics as a test target
Dolphin drives the diagnostic scenarios a software change can silently break: UDS services and sessions, fault codes that must set and clear, security access, and the reprogramming path, end to end.
- 02
Communication-stack layers and software download
Automated tests of different layers of a communication stack, and of higher-level sequences such as software download. It is how Diadrom verifies its own Bootloader.
- 03
One suite, in the pipeline and on the rig
The same test cases run against virtual ECUs in the CI pipeline and against real ECUs on the HIL rig, so the fast check and the faithful one never drift apart.
- 04
Every commit under test
In the CI chain every commit is built and tested automatically, with module-level CI feeding system-level CI. Regressions surface in minutes, not at the end of a manual cycle.
- 05
Configured once, version-controlled
Test execution is configured in the GUI, exported and version-controlled, and kept in sync across platforms, so the same suite runs the same way on every build.
- 06
The bench, not just the bus
Dolphin controls external equipment that has an API, such as power supplies and multimeters, as part of a test. It is not tied to a particular hardware interface.
- 07
One expected behaviour, every supplier
When many suppliers implement the same security concept, a shared automated suite verifies every implementation against the same expected behaviour, with the security tests traced to requirements and ready for audit.
For the engineers in the room
What it tests, where it runs.
- Tests
- UDS (ISO 14229) services and sessions · fault codes set and cleared · security access · the reprogramming sequence · different layers of the communication stack · software download
- Runs in
- CI chains, on every commit · HIL rigs · against virtual and real ECUs
- Equipment
- External instruments with an API, such as power supplies and multimeters; not tied to a particular hardware interface
- Configuration
- Built in the GUI, exported and version-controlled, kept in sync across platforms
- Evidence
- Security tests traced to requirements, ready for audit
Supported interfaces, scripting and report formats are not published here. Ask us below.
Proof
A three-day build, now an hour.
100%of test cases automated
Watch the proof · 1:02Illustration, AI-generated
Licensing
Two ways to take Dolphin.
- 01
Alongside a Diadrom development team
Dolphin licences together with a Diadrom team working in your programme. How a team engagement works.
- 02
With a bounded project
Dolphin licences with a bounded delivery on Diadrom's mandate: you set the outcome and the acceptance criteria. How a bounded delivery works.
Licences are perpetual or term-based, agreed per programme. Source-code escrow is available. Support and further development run under a maintenance agreement. More on how our products are licensed.
Read deeper
The engineering behind it.
Related products
Dolphin verifies the Bootloader and Diag Com Stack, and works beside DiagStudio.
Ask us
Question about Dolphin?
Two fields, straight to the engineers. We reply within one business day.