Refine
Review
- peer-review (1)
Open Access
- nein (1)
Document Type
- Conference Paper (1)
- Master's Thesis (1)
Institute
Language
- English (2)
The Automotive Industry has been investing vast resources towards the development of Automated Driving Systems (ADS) and Advanced Driver Assistance Systems (ADAS) in recent years. The competition between different Automobile OEMs in this direction has led to the fast growing research in both the development and validation of such complex systems. This evolution of mobility has been obviously reflected in the adaptation of many academic related automotive studies, with a growing focus on the technology and science assisting in the engineering of these systems, rather than the saturated knowledge in the scope of conventional automotive systems. On another side, and to cope with this huge expansion, different standards are evolving to support and collaborate the process of developing ADS and ADAS, shedding light on what the future of mobility would look like.
Without the proper validation and testing of released ADS and ADAS functions, they cannot reach the state of deployment in production level. Considering the different validation platforms in a test environment and the enormous number of test cases, test automation tools have been used to facilitate the process of testing, assigning verdicts and analysing the trace outputs of a test case execution. These tools are even capable of exporting test reports to databases for monitoring of the complete test process and providing feedback against test management tools. However, it has been highly inefficient and slow to have a custom implementation of test cases for a specific platform. Thus, it has always been fundamental to have test cases on an abstract level from the test environment platform, giving the opportunity to reuse test cases on different validation stages and cross checking their verdicts, which in return improves the tracking of defects and reporting them to the function developers.
The current validation process of ADS and ADAS starts with Hardware in the Loop (HiL) test environment using Tracetronic test automation tool (ECU-Test). A test management tool provides a database of test cases in a human readable form. According to the Test Design Specification (TDS) for the validation of a specific software release, only the required human readable test cases are used for creating ECU-Test runnable test cases (test packages).
In this work, a Software in the Loop (SiL) test environment with a different toolchain is utilized and made compatible for testing with ECU-Test test cases reusing the same test artifacts, i.e. scnearios, roads and catalogs, used for testing on HiL test environment. The SiL environment consists of all the required models, i.e. sensors’ models and vehicle dynamics model, in addition to the System Under Test (SUT) and the environment simulator. In an aim of having the test cases in an absolute abstract form, apart from the test platform, the concept of keyword-based test steps is embraced for creating test cases without any dependency to the test platform, i.e. HiL and SiL platforms. Furthermore, SiL implementation packages with SiL specific test steps are developed for mapping against their respective keywords. Finally, results from the developed abstract test case executed on the SiL platform are compared to the ones available from the existing HiL test case with the same test artifacts.
Out of scope for this research and future work includes the creation of HiL specific implementation packages for linking with the abstract test case, hence executing the same abstract test case developed in this work on the HiL platform.