Description

  • Overview
  • Business objectives
  • Learning Objectives
  • Course Contents
  • Exam Details

ISTQB FOUNDATION – AUTOMOTIVE SOFTWARE TESTER COURSE is designed for professionals who are working within automotive projects.
It is also for professionals who are planning to start implementing special automotive testing techniques in the near future, or are working within companies that plan to do so. The certification provides an advantage for those who would like to know the required Automotive activities, roles, techniques, and methodologies specific to their role.

  • Collaborate effectively in a test team.Adapt the test techniques known from the ISTQB® Certified Tester Foundation Level (CTFL®) to the specific automotive project  requirements.
  • Consider the basic requirements of the relevant automotive standards (Automotive SPICE®, ISO 26262, etc.) and select suitable test techniques.
  • Apply the virtual test methods (e.g. HiL, SiL, MiL, etc.) in test environments.

    • 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 an 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 for the testing with the help of 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 Vmodel.
      Static test techniques

    • The tester should be able to explain the purpose, the types and obligations of the MISRAC: 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.

  • 1 Introduction
    1.1 Requirements from divergent project objectives and increasing product complexity
    1.2 Project aspects influenced by standards (K1)
    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
    3.2.2 Software in the Loop
    3.2.3 Hardware in the Loop
    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

Similar to the Foundation Level Certification Core exam, the Specialist Automotive Software Tester Certification exam will comprise of 40 multiple choice questions, with a pass mark of 65% to be completed within 60 minutes.

The Foundation Level Core Certificate is a precondition of the CTFL Automotive Software Tester Certificate.

What is included with this course?

Inclusions Classroom Live Online Description
No Hidden Cost
V
V
Our price is including course fee and GST.
Pass Guarantee
V
V
On the rare occasion a student doesn’t pass, they can re-sit training course in Free of charge. (T&C apply)
Course Manual
V
V
We will provide 400 pages+ course manual for your reference.
Food & Beverages
V
V
Full catering is provided including morning tea, lunch afternoon tea.
Online Version
V
V
Full access to online version of training for self-study
Sample Practice Exam
V
V
Sample Practice Exam are provided at the end of each chapter and full exam sets after completion of course.
Study Resources
V
V
35,000 Study resources are provided including Articles, ebooks and software testing tools.
Certified Trainer
V
V
All our trainers are certified Trainer.
blank

Pass Guarantee with confidence

blank

Sample Practice Exam

blank

400+ Pages Course Manual

blank

35,000 Study Resources

blank

Authorized Training Center

Classroom Training : Location

In-House Training

Dates Location Why Price
Your Choice
At your place
Upskill your team with training delivered at a location