Abstract

Automotive test case specifications document test cases to be performed for a specific test object at a defined test level. They are a fundamental part of a structured automotive testing process, as required by the ISO 26262. The aim of our research is to identify challenges from a practitioner’s point of view that lead to poor quality of test case specifications and thus negatively impact time, cost, and probability of defect detection. We designed an exploratory case study to systematically identify challenges focusing on (C) creation, (P) processing, and (Q) quality assurance related aspects of test case specifications. We conducted 17 semi-structured interviews covering a German OEM as well as three of its automotive suppliers and analyzed them qualitatively. We investigated causes and consequences arising from the challenges. Additionally, we conducted a descriptive survey to assess frequency and criticality. The identified challenges were summarized in a taxonomy consisting of nine main categories: (1) availability and (2) content-related problems with input artifacts, problems related to (3) a lack of knowledge, (4) the test case description, (5) the test case specification content, (6) processes, (7) communication, (8) quality assurance, and (9) tools. The challenges were assessed by 26 internal and 10 external employees. Hence, we identified differences between these groups in terms of access to documents, incomplete requirements, scope of model series, process, and tool-related aspects. Overall, the study results underline the necessity of quality assurance measures for test case specifications. Based on the assessments, our research indicates a broad range of test case description related challenges that are promising candidates for improving test case specification quality.

Highlights

  • Nowadays, innovation in vehicles is mainly realized by software and electronic systems

  • We identified the distribution (ToC-1.2, 5.1.2) and access restrictions of input artifacts (ToC-1.3, 5.1.3) especially in collaboration with suppliers as new challenges concerning test case specification, which were not mentioned in related work

  • We described the design and implementation of two studies in order to identify and describe challenges in the field of automotive test case specifications

Read more

Summary

Introduction

Innovation in vehicles is mainly realized by software and electronic systems. In addition to a systematic development process, standards require a mandatory documentation of the activities and relevant work products. In the context of test documentation, these work products are a verification plan and a verification specification. The latter is called test case specification in the software testing standard ISO 29119 (2013) and this term will be used in this article. We provide a brief overview of important aspects of the test process in automotive software development. Automotive software testing in general follows the fundamental test process (Spillner et al 2014), which consists of five phases: test planning, test analysis & design, test implementation & execution, evaluation & reporting, and test closure activities (see Fig. 2).

Objectives
Results
Discussion
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call