It is always crucial to test new functionality as soon as possible to make sure it does not have a negative impact on the existing features. Our experience has shown that continuous integration is a viable approach when developing complex embedded systems. It usually means that you must invest effort in developing an integrated Automated Build System (ABS) and an Automated Testing System (ATS), but it also results in less effort required for testing and bug fixing. This approach enabled us to create high quality and reliable solutions.
A common preconception is that "automated tests do not work in embedded development".
Due to the diversity of embedded systems there is no general approach to test automation and it requires much effort. Sometimes it is not feasible or possible to automate tests at all. But on the other hand, because it is quickly dismissed, people don't see the real benefits of test automation.
Working at Comtrade Digital Services is exciting because you come across a wide variety of software projects from different domains. In this dynamic working environment you are inevitably exposed to practices like Continuous Integration, Continuous Deployment, DevOps, Agile…
But for someone coming from an embedded background, they were more buzzwords than viable practices that can be used in the development process. Why is this so?