Deployment of Continuous Integration and Continuous Testing in Mobility for Software Qualification Test

<div class="section abstract"><div class="htmlview paragraph">In the rapidly evolving field of automotive engineering, the drive for innovation is relentless. One critical component of modern vehicles is the automotive ECU. Ensuring the reliability and performance of ECU is paramount, and this has led to the integration of advanced testing methodologies such as Hardware-in-the-Loop (HIL) testing. In conjunction with HIL, the adoption of Continuous Integration (CI) and Continuous Testing (CT) processes has revolutionized how automotive ECU are developed and validated. This paper explores the integration of CI and CT in HIL testing for automotive ECU, highlighting the benefits, challenges, and best practices.</div><div class="htmlview paragraph">Continuous Integration and Continuous Test (CI/CT) are essential practices in software development. <b>Continuous Integration</b> process involves regularly integrating code changes into the main branch, ensuring that it does not interfere with the work of other developers. The CI/CT server automatically build and test code whenever a new commit is done. The primary goal is to minimize defects and conflicts during the integration of the entire project. Jenkins is one of the automation servers which has been used in automotive programs. <b>Continuous Test</b> is the deployment of automated testing on automotive ECU software by selection of appropriate test environment such as HIL to perform required test cases. By adopting CI/CT, development teams can receive early feedback on delivered software which will lead to less defects and deliver high-quality software. CI/CT methodology provides rapid feedback, facilitating swift problem identification and resolution before they escalate into major challenges.</div></div>