From a three-day manual build to a one-hour automated one

As more of a vehicle's behaviour moves into software, the bottleneck moves to verification. Teams ship changes continuously, but a release is only as fast as the slowest manual step in front of it — and for embedded ECU software that step is usually testing. Continuous integration, where every change is built and tested automatically, is how the rest of the software world removed that bottleneck; the automotive industry is now applying it to embedded software, where the cost of a late-discovered regression is higher.

Mitsubishi Electric (MELCO) develops the infotainment head unit (IHU) for a Volvo Cars platform (SPA) — a feature-rich ECU whose software has to keep pace with an agile programme. The team wanted to develop and verify in parallel rather than in sequence, but its release build was a manual, multi-day effort and testing happened too late to catch problems cheaply.

Producing a release meant roughly three days of manual work, and tests were run by hand rather than on every change. That made releases slow and regressions expensive: a defect introduced early might not surface until the end of a manual cycle, when it is hardest and most costly to fix. The team needed every test case automated and the release build itself made repeatable and fast — without lowering the verification bar a vehicle ECU demands.

Diadrom ran a pre-study and then implemented an automated continuous-integration chain for the ECU software — module-level CI feeding system-level CI, so each change is built and integrated automatically. Verification was automated with Diadrom Dolphin: test execution configured through Dolphin's interface, exported and version-controlled, and kept in sync across platforms, so the same suite runs the same way on every build.

The result is a pipeline where every commit is built and tested automatically, and producing a release is a roughly one-hour automated run instead of three days of manual assembly — the agile 'develop and verify in parallel' model made real for a complex vehicle ECU.

The pipeline turned verification from the slowest step into an automatic one. Every commit is now built and tested without anyone waiting on it, and the release that once took three days of manual work runs in about an hour — so the team releases more often, catches regressions while they are cheap to fix, and holds an agile pace without lowering the bar a vehicle ECU demands. It is the same verification discipline Diadrom builds into its products, applied to a customer's own development process.

As vehicles become more software-defined, the teams that win are the ones that can change software quickly and prove it still works — continuously. The lesson generalises: automate the build and the verification together, put every commit under test, and 'fast' and 'safe' stop being a trade-off.