Use Case: Continuous Integration and Testing for SIL and HIL

The Task

More complex ECU functionality and the growing number of ECU variants increase the amount and complexity of testing for ECU software validation. To implement an efficient test process that masters this challenge, software developers and testers have to cooperate closely. For this purpose, processes already established in general software development, such as agile development with continuous integration and continuous testing, are making their way into ECU software development. This calls for test management for ECU testing and an intelligent process automation tool, such as SYNECT. 

The Challenge

• Meeting tight and accelerating release schedules
• Ensuring that the correct models, including variant-specific parts and parameterizations, are used for the automatic build
• Ensuring that new or modified models are automatically included in nightly builds
• Having the right ECU software build, real-time application, and parameterization on the test system and trigger the relevant tests

The Solution

SYNECT ensures that the right chain of actions is processed when individual artifacts are modified. It also evaluates the relevant variant dependencies. Actions include the rebuild of model containers after a model is checked in, or the use of these containers during a recurring nightly build of the real-time application. It is also possible that a new version of ECU software, provided only via a configuration management system, must trigger a set of regression tests using the latest build of the real-time application on the HIL system and the proper parameterization corresponding to the ECU software variant. The high automation SYNECT offers in this regard speeds up the development and test cycle, reduces error-prone manual work, and automatically provides full traceability between all the artifacts used in the process.