CERTIFIED TESTER AUTOMOTIVE SOFTWARE TESTER (CT-AuT)
- Description
- Reviews
CERTIFIED TESTER AUTOMOTIVE SOFTWARE TESTER (CT-AuT)
COURSE DESCRIPTION
The ISTQB® Certified Tester Automotive Software Tester (CT-AuT) certification focuses on the specific requirements for “testing E/E systems” in the automotive environment on the basis of established standards (Automotive SPICE®, ISO 26262, AUTOSAR®, etc.). It also covers testing in virtual environments (including XiL), and automotive-specific static and dynamic test techniques.
COURSE OBJECTIVES
Foundation Level testers who have passed the “CTFL Automotive Software Tester Specialist” syllabus exam should be able to accomplish the following Business Objectives:
• 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.
WHO CAN BENEFIT
The Automotive Software Tester certification is aimed at anyone involved in software testing in the automotive area including testers, test analysts, test engineers, test consultants, test managers, release testers, and software developers. It may also be useful to people in the role of project manager, quality manager, software development manager, system analyst (business analysts), IT manager or management consultants, who wish to acquire basic knowledge and basic understanding of the topic software testing in the automotive area.
PREREQUISITES
To gain this certification, candidates must hold the Certified Tester Foundation Level certificate.
COURSE OUTLINE
1 Introduction
1.1. Requirementsfrom divergent project objectives and increasing product complexity
1.2. Project aspects influenced by standards
1.3. The six generic phrases 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 lifecycle
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 [informative]
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. Essentia; interfaces, databases and communication protocols of an 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 Guideline
4.1.2. The Quality characteristicsfor 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
Please contact us for schedules and for booking a private class.
Popular Courses
Archive
Working hours
Monday | 9:00 am - 6.00 pm |
Tuesday | 9:00 am - 6.00 pm |
Wednesday | 9:00 am - 6.00 pm |
Thursday | 9:00 am - 6.00 pm |
Friday | 9:00 am - 6.00 pm |
Saturday | Closed |
Sunday | Closed |