ISTQBCertified Tester Automotive Software Tester
The ISTQB® Certified Tester Automotive Software Tester (CT-AuT) certification validates your ability to test E/E systems in the automotive domain, applying established standards like Automotive SPICE®, ISO 26262, and AUTOSAR®. It covers testing in virtual environments (XiL) and automotive-specific static and dynamic test techniques. This certification is for testers and developers working on automotive software who need to ensure safety, reliability, and compliance in increasingly complex vehicle systems.
606 practice questions · Updated 2026-07-30
4Domains
25Objectives
156Concepts
606Questions
CT-AUT Curriculum
Every domain, objective, and concept the CT-AUT exam measures.
- Standards in Automotive Software Testing
- Impact of Standards on Project Planning
- Impact of Standards on Process and Documentation
- Impact of Standards on Tooling and Infrastructure
- Impact of Standards on Roles and Responsibilities
- System lifecycle phases
- Phase purposes
- Phase interactions
- Tester's role in release process
- ASPICE Overview
- Process Assessment Model
- Process Capability Levels
- Testing Processes in ASPICE
- Verification and Validation
- Test Strategy and Planning
- Traceability in Testing
- Test Documentation
- Test Execution and Reporting
- Integration with Other Processes
- Purpose and scope of ISO/IEC 29119
- Key definitions and terminology
- Test process models
- Test documentation requirements
- Test techniques and coverage criteria
- Test management and reporting
- Application to automotive software testing
- ISO 26262 Overview
- Vocabulary and Key Terms
- Management of Functional Safety
- Concept Phase
- System-Level Development
- Hardware-Level Development
- Software-Level Development
- Production and Operation
- Supporting Processes
- ASIL and Risk Classification
- Safety Validation and Confirmation Measures
- Safety Case and Release for Production
- Functional safety standards
- Safety culture in testing
- Roles and responsibilities
- Safety lifecycle
- Hazard and risk analysis
- Safety requirements testing
- Safety mechanisms testing
- Safety case and evidence
- Role of tester in safety lifecycle
- Safety lifecycle phases and testing activities
- Tester involvement in safety requirements
- Test planning aligned with safety standards
- Verification and validation in safety context
- Traceability of safety requirements to tests
- Handling safety anomalies and defects
- Documentation and reporting for safety audits
- Criticality and test extent relationship
- Risk-based test prioritization
- Test depth and coverage levels
- Regulatory and safety standards impact
- Resource allocation for critical systems
- AUTOSAR Overview
- AUTOSAR Architecture Layers
- AUTOSAR Basic Software Modules
- AUTOSAR Interfaces and Ports
- AUTOSAR RTE (Runtime Environment)
- AUTOSAR Methodology and Workflow
- AUTOSAR Testing Considerations
- Purpose of ASPICE
- Purpose of ISO 26262
- Scope of ASPICE
- Scope of ISO 26262
- Relationship between ASPICE and ISO 26262
- Integration of ASPICE and ISO 26262 in testing
- Key differences between ASPICE and ISO 26262
- Test levels in automotive software testing
- Comparison criteria for test levels
- Test level objectives and scope
- Test level environment and tools
- Test level artifacts and deliverables
- Test level dependencies and sequencing
- Test level roles and responsibilities
- Test level traceability and coverage
- Test level selection and tailoring
- Purpose of test environments in virtual testing
- Components of a virtual test environment
- Types of virtual test environments
- Advantages and limitations of virtual test environments
- Integration of virtual test environments in the development process
- Definition of Closed-Loop Testing
- Definition of Open-Loop Testing
- Key Differences Between Closed-Loop and Open-Loop
- Applications of Closed-Loop Testing
- Applications of Open-Loop Testing
- Advantages and Disadvantages of Each Approach
- Impact on Test Design and Execution
- XiL test environments overview
- Selecting appropriate XiL environment
- Setting up XiL test environments
- Executing tests in XiL environments
- Analyzing XiL test results
- Advantages and limitations of XiL testing
- MiL definition and purpose
- MiL test environment setup
- MiL test execution
- MiL test analysis and evaluation
- MiL limitations and benefits
- Definition of SiL
- SiL vs. HiL
- SiL Test Environment Setup
- SiL Test Execution
- Benefits and Limitations of SiL
- SiL in Automotive Software Development
- HiL fundamentals
- HiL system architecture
- Plant modeling for HiL
- Sensor and actuator simulation
- Real-time requirements
- HiL test setup and configuration
- Test execution and automation
- Failure injection and fault simulation
- HiL test result analysis
- Advantages and limitations of HiL
- XiL test environment definitions
- Comparison criteria for XiL environments
- Advantages and limitations of each XiL environment
- Selection of appropriate XiL environment
- Purpose and Scope of MISRA-C:2012
- Structure of MISRA-C:2012
- Compliance Levels
- Categorization of Rules
- Key Rule Categories
- Applying MISRA-C:2012 in Testing
- Common Violations and Pitfalls
- Tooling and Automation
- Documentation and Deviation Process
- Quality characteristics for requirements reviews
- Applying quality characteristics in reviews
- Definition of Back-to-Back Testing
- Comparison of Model and Code Behavior
- Test Execution and Result Evaluation
- Handling Differences and Tolerances
- Integration into Test Process
- Fault injection fundamentals
- Fault models
- Fault injection techniques
- Fault injection in automotive contexts
- Safety and reliability impact
- Test execution and analysis
- Requirements-based testing fundamentals
- Traceability of requirements to test cases
- Deriving test cases from requirements
- Handling ambiguous or incomplete requirements
- Coverage criteria for requirements-based testing
- Reviewing requirements for testability
- Context factors for test technique selection
- Mapping techniques to contexts
- Combining test techniques
Ready to practice?Test your knowledge with exam-style questions or take an intelligent quiz tailored to your level.
Percentages reflect share of the current practice bank, not official exam weightings — no structured per-skill weight is published for CT-AUT, so none is invented.