1 Introduction

1.1 Requirements from divergent project objectives and increasing product complexity

1.2 Project aspects influenced by standards

1.3 The six generic phases in the system lifecycle

1.4 The contribution/participation of the tester in the release process

2 Standards for the testing of E/E systems

2.1 Automotive SPICE (ASPICE)

2.1.1 Design and structure of the standard

2.1.2 Requirements of the standard

2.2 ISO 26262

2.2.1 Functional safety and safety culture

2.2.2 Integration of the tester in the safety lifecyle

2.2.3 Structure and test specific parts of the standard

2.2.4 The influence of criticality on the extent of the test

2.2.5 Application of content from CTFL® in the context of ISO 26262

2.3 AUTOSAR

2.3.1 Objectives of AUTOSAR

2.3.2 General structure of AUTOSAR

2.3.3 Influence of AUTOSAR on the work of the tester

2.4 Comparison

2.4.1 Objectives of ASPICE and ISO 26262

2.4.2 Comparison of the test levels

3 Testing in a virtual environment

3.1 Test environment in general

3.1.1 Motivation for a test environment in the automotive development

3.1.2 General parts of a test environment

3.1.3 Differences between Closed-Loop and Open-Loop

3.1.4 Essential interfaces, databases and communication protocols of a electronic control unit

3.2 Testing in XiL test environments

3.2.1 Model in the Loop (MiL)

3.2.2 Software in the Loop (SiL)

3.2.3 Hardware in the Loop (HiL)

3.2.4 Comparison of the XiL test environments

4 Automotive-specific static and dynamic test techniques

4.1 Static test techniques

4.1.1 The MISRA-C: 2012 Guidelines

4.1.2 Quality characteristics for reviews of requirements

4.2 Dynamic test techniques

4.2.1 Condition testing, multiple condition testing, modified condition/decision testing

Decision outcome for the expression

4.2.2 Back-to-Back-Testing

4.2.3 Fault injection testing

4.2.4 Requirements-based testing

4.2.5 Context-dependent selection of test techniques