ISTQB CT-AuT study guide
ISTQB CT-AuT · Work through your exam, one topic at a time.
The ISTQB® Certified Tester Automotive Software Tester (CT-AuT) is a specialist-level qualification in the ISTQB® portfolio. As ISTQB® describes it, the 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.)" and "also covers testing in virtual environments (including XiL), and automotive-specific static and dynamic test techniques." That scope makes it relevant to testers, test analysts, test engineers and test managers working on electronic/electrical (E/E) systems in vehicle development, and to professionals moving from general software testing into the automotive domain. The ISTQB CT-AuT study guide has 4 sections and about 1,487 words.
01Testing E/E Systems in the Automotive Environment Based on Established Standards
This domain checks whether you can connect Automotive SPICE®, ISO 26262, and AUTOSAR® to concrete test planning. You must know what each standard requires, what it leaves to the organization, and how those requirements change test scope, rigor, and evidence.
393 words, about 2 min02Testing in Virtual Environments (Including XiL)
Virtual testing and XiL: you must distinguish MiL, SiL, PiL, HiL, and ViL, explain what each can and cannot validate, and choose an appropriate level for a given test objective. XiL is an umbrella term for “X-in-the-loop.” The X is the test object: model, software, processor, hardware, or vehicle.
409 words, about 2 min03Automotive-Specific Static Test Techniques
Automotive static techniques: reviews and static analysis applied to requirements, architecture, models, and code, with emphasis on standards compliance, traceability, and safety. Static testing does not execute the test object.
346 words, about 2 min04Automotive-Specific Dynamic Test Techniques
Dynamic test techniques used in automotive testing: black-box and white-box methods, fault injection, back-to-back testing, robustness, and timing tests across unit, integration, system, and acceptance levels. Classical black-box techniques apply: equivalence partitioning, boundary value analysis, decision tables, state transition testing, and use case or scenario testing.
339 words, about 2 min