Certified Automotive Software Testers should be able to demonstrate their skills in the following areas:

Introduction

• The tester should be able to explain and give examples of the challenges of automotive product development that arise from divergent project objectives and increasing product complexity.

• The tester should be able to recall project aspects that are influenced by standards such as time, cost, quality and project/product risks.

• The tester should be able to recall the six generic phases in the system life cycle per ISO/IEC 24748-1

• The tester should be able to recall the contribution and the collaboration of the tester in the release process.

ASPICE

• The tester should be able to recall the two dimensions of Automotive SPICE® (ASPICE).

• The tester should be able to explain the Capability levels 0 to 3 of ASPICE.

• The tester should be able to explain the meaning of the 4 rating levels and the capability indicators of ASPICE from the test perspective.

• The tester should be able to explain the requirements of ASPICE for the test strategy including the regression test strategy.

• The tester should be able to recall the requirements of ASPICE for the test documentation.

• The tester should be able to design a verification strategy (in contrast to a test strategy) and criteria for unit verification.

• The tester should be able to explain the different traceability requirements of ASPICE from the test perspective.

ISO 26262

• The tester should be able to explain the objective of functional safety for E/E systems.

• The tester should be able to recall his contribution as a tester for the safety culture.

• The tester should be able to recall his contribution as a tester for the safety culture.

• The tester should be able to present the role of the tester in the framework of the safety life cycle per ISO 26262.

• The tester should be able to recall the volumes (part titles) of ISO 26262 that are relevant for him.

• The tester should be able to recall the criticality levels of ASIL.

• The tester should be able to explain the influence of ASIL on applicable test design techniques and test types for static and dynamic tests and the resulting test extent.

• The tester should be able to apply the selected method table of the ISO 26262.

AUTOSAR

• The tester should be able to recall the objectives of AUTOSAR.

• The tester should be able to recall the influences of AUTOSAR on the work of the tester.

Comparison

• The tester should be able to recall the different objectives of ASPICE and ISO 26262.

• The tester should be able to explain the differences between ASPICE, ISO 26262, and CTFL® regarding the test levels.

Test Environment in General

• The tester should be able to recall the purpose/the motivation of a test environment in the automotive environment.

• The tester should be able to recall the general parts of an automotive-specific test environment.

• The tester should be able to recall the differences between Closed-Loop systems and Open-Loop systems.

• The tester should be able to recall the essential functions, databases and protocols of an electronic control unit (ECU).

Testing in XiL environments

• The tester should be able to recall the structure of a MiL test environment.

• The tester should be able to explain the application area and the boundary conditions of a MiL test environment.

• The tester should be able to reproduce the structure of a SiL test environment.

• The tester should be able to recall the structure of an HiL test environment.

• The tester should be able to explain the application areas and the boundary conditions of an HiL test environment.

• The tester should be able to summarize the advantages and disadvantages of the testing with the help of the criteria of the XiL test environments (MiL, SiL, and HiL).

• The tester should be able to apply criteria for the assignment of a given test scope to one or more test environments.

• The tester should be able to classify the three XiL test environments (MiL, SiL, HiL) in the V-model.

Static test techniques

• The tester should be able to explain the purpose, types, and obligations of the MISRA C: 2012 programming guideline with the help of examples.

• The tester should be able to apply a review of requirements with the quality characteristics of the ISO/IEC 29148 that are relevant for him.

Dynamic test techniques

• The tester should be able to create test cases to achieve modified condition/decision testing coverage.

• The tester should be able to explain the use of back-to-back testing by giving examples.

• The tester should be able to explain the principle of fault injection tests by giving examples.

• The tester should be able to recall the principles of requirement-based testing.

• The tester should be able to apply context-dependent criteria for the choice of suitable and necessary test design techniques.