CT-AuT — Automotive Software Tester glossary

101 terms the exam expects you to know, defined in plain language.

A

ASIL Decomposition(asil decomposition): A technique to reduce the integrity level of a component by splitting a hazard across sufficiently independent elements.
ASIL Determination(asil determination): The process of assigning an ASIL based on three parameters: severity, exposure, and controllability.
ASIL and Automotive SPICE Influence on Technique Selection(influence of asil and automotive spice): The combined guidance from ASIL and Automotive SPICE that determines which test techniques to apply based on risk and rigor requirements.
AUTOSAR(autosar): A standardized software architecture for automotive ECUs that separates application software from hardware through a layered architecture.
Automated regression testing(automated regression testing): Repeated execution of tests to detect regressions, facilitated by SiL's speed and automation.
Automotive SPICE(automotive spice, aspice): A process assessment model used to evaluate the capability of software development processes in the automotive industry.
Automotive SPICE (ASPICE)(automotive spice, aspice): A process capability model that requires a defined test strategy with systematic test technique selection based on risk.
Automotive SPICE test strategy(aspice test strategy): A defined approach in ASPICE for selecting test techniques based on risk and project context.
Automotive Safety Integrity Level(asil): A risk classification scheme defined by ISO 26262 that determines safety requirements and testing rigor.
Automotive Safety Integrity Level (ASIL)(asil, asil level, asil levels, automotive safety integrity level): A classification of hazards into four levels (A, B, C, D) based on severity, exposure, and controllability, determining the rigor of safety measures.

B

Back-to-back comparison testing(back-to-back comparison testing): A test technique comparing outputs of different implementations to detect inconsistencies, recommended for ASIL D.
Back-to-back testing(back-to-back testing): A verification technique that compares model behavior with code behavior to ensure consistency.
Boundary value analysis(boundary value analysis, bva): A test design technique that focuses on test cases at the boundaries of input partitions.

C

Capability Levels(capability level, capability scale): A six-level scale from Level 0 (Incomplete) to Level 5 (Innovating) that rates process maturity in Automotive SPICE.
Closed Loop Test Environment(closed loop test environment, closed loop configuration, closed loop testing, closed loop, closed-loop environment, closed loop environment): A test configuration where the system under test is embedded in a simulation with feedback from outputs to inputs.
Compile-Time Injection(compile-time injection): A type of fault injection that modifies source code or model before compilation.
Component-Level Fault Injection(component-level fault injection): Fault injection applied to a single electronic control unit (ECU) or component.
Control system testing(control system validation): Testing of systems where outputs affect inputs, requiring closed loop for realistic validation.

D

Divergent Project Objectives(conflicting objectives): Conflicting goals in automotive projects such as cost reduction, time-to-market, safety compliance, and innovation.
Dynamic Requirements-Based Testing(dynamic requirements-based testing, dynamic rbt): A form of RBT that executes software against test cases derived from requirements, using techniques like EP, BVA, and state transition.
Dynamic interaction testing(dynamic test, interactive testing): Testing that validates system behavior under realistic, feedback-driven conditions.

E

Electronic Control Unit(ecu): An embedded system in vehicles that controls one or more electrical systems or subsystems.
Electronic Control Unit (ECU) simulation(electronic control unit simulation, ecu simulation): The simulated behavior of hardware that runs the production code in a SiL environment.
Equivalence partitioning(equivalence partitioning, ep): A systematic test design technique that divides input data into partitions from which test cases are derived.
Equivalence partitioning with boundary value analysis(equivalence partitioning, boundary value analysis): A systematic test design technique that divides input data into partitions and tests boundaries.
Evidence-based assessment(evidence based assessment): The principle in Automotive SPICE that assessments require demonstration that processes are followed, not just documented.

F

Fault Injection Testing(fault injection testing, fault injection, fault injection test): A testing technique required for ASIL C and D that introduces faults to verify system robustness.
Fault Model(fault model): A representation of potential faults derived from safety analysis (e.g., FMEA, FTA) to guide fault injection testing.
Fault injection(fault injection): A test technique that deliberately introduces faults to verify system behavior, recommended for high ASIL.
Fault injection in HiL(fault injection, hil fault injection): The capability of HiL to inject faults and simulate realistic failure conditions for testing safety-critical functions that are too dangerous for road tests.
Feedback Loop(feedback path, feedback loop): A path through which system outputs influence subsequent inputs in a simulation.
Functional testing(functional testing): Verification of software functionality using SiL, often executed early in development.

G

Graceful Degradation(graceful degradation): A system behavior where functionality is reduced but maintained in a safe manner under fault conditions.

H

Hardware-in-the-Loop(hil, hil): A testing method where real hardware is used in a simulated environment to verify timing and hardware interaction.
Hardware-in-the-Loop (HiL)(hil, hardware-in-the-loop, hil testing): A test environment where a real ECU is connected to a real-time simulation of the vehicle and its environment for high-fidelity system-level validation.
Hardware-in-the-Loop Testing(hil testing, hil): A test method that connects the real ECU to a real-time simulation of the vehicle environment for high-fidelity system validation.
Hazard Analysis and Risk Assessment(hazard analysis and risk assessment): A process that identifies hazards and defines safety requirements, forming the basis for RBT in automotive.
Host computer simulation(host computer simulation): Execution of embedded software on a non-real-time host computer that mimics ECU behavior.
Hybrid test configuration(hybrid testing): A test approach that combines open loop for some inputs and closed loop for others.

I

ISO 26262(iso 26262, iso 26262 standard): The international standard for functional safety of electrical and electronic systems in road vehicles, covering the entire safety lifecycle.
ISO 26262 test technique selection tables(table 9, table 10): Tables in ISO 26262 that list recommended test techniques for different ASIL levels.
ISO 26262 verification process(iso 26262 verification process): A safety standard framework for verifying automotive software, employing SiL for functional tests.
ISTQB glossary(istqb glossary): A reference source for standard definitions of test techniques used to align terminology across standards.
Increasing Product Complexity(product complexity): Growth in the number of ECUs and software features leading to more interactions and potential failure modes.
Independence in Testing(independence in testing): The principle that higher ASIL levels require greater organizational independence between test and development teams.

M

Model-in-the-Loop(mil, model-in-the-loop testing, mil testing): A testing method where algorithms are tested as models, without actual production code or hardware.
Model-in-the-Loop (MiL)(mil, model-in-the-loop, mil testing): A test method that validates control algorithms using plant models early in development, allowing fast iteration without hardware.
Model-to-Code Migration(model-to-code migration): A development scenario where code is automatically generated from a model and back-to-back testing verifies behavioral equivalence.
Modified Condition/Decision Coverage(modified condition/decision coverage, mc/dc): A coverage criterion requiring each condition to independently affect the decision outcome, used for ASIL C/D.

O

Open Loop Test Environment(open loop test environment, open loop configuration, open loop testing, open loop, open loop environment): A test configuration with predefined input stimuli and no feedback from outputs to inputs.

P

Permanent Fault(permanent fault): A persistent fault such as a stuck-at fault that remains in the system.
Plant model(plant model, plant models, environment model): A mathematical representation of the environment (sensors, actuators, vehicle dynamics) used in simulation-based testing.
Plant models(plant models): Simulated representations of the environment required for SiL; inaccuracies can lead to misleading results.
Platform Porting(platform porting): The process of moving software to a different platform, where back-to-back testing ensures functional equivalence.
Process Assessment Model(process assessment model, pam, process assessment model (pam)): A formal model that maps processes to capability indicators for performing assessments in Automotive SPICE.
Process Reference Model(process reference model, prm): The model that organizes processes into categories covering the software development lifecycle, including acquisition, development, and support.
Process capability in ASPICE(process capability): The focus of Automotive SPICE on assessing the maturity and capability of development processes.

Q

Quality Management (QM)(qm, quality management): A classification indicating that no special safety measures are required beyond standard quality management.

R

Real Vehicle Testing(real vehicle testing): A testing method that drives a production-intent vehicle on test tracks or public roads to achieve the highest realism for final validation.
Real-Time Simulation(real-time simulation): A simulation that runs at the same speed as the real system, used in HiL to test the ECU realistically.
Real-time behavior limitation(real-time behavior limitation): The inability of SiL to verify timing behavior because it runs on a non-real-time OS.
Reference Version(reference version): A trusted implementation, such as a simulation model or legacy system, used as the baseline for comparison in back-to-back testing.
Regression Fault(regression faults): A defect introduced during code changes that back-to-back testing is especially effective at detecting.
Requirements-based Testing(requirements-based testing, rbt): A testing technique highly recommended for all ASIL levels, deriving test cases from requirements.
Runtime Injection(runtime injection): A type of fault injection that introduces faults during system execution through software or hardware means.

S

SWE.5 (Software Integration Test)(swe.5, software integration test): A development process in Automotive SPICE that defines expected outcomes for software integration test activities.
SWE.6 (Software Qualification Test)(swe.6, software qualification test): A development process in Automotive SPICE that defines expected outcomes for software qualification test activities.
Safe State(safe state): An expected system state defined in the safety concept, entered upon fault detection to avoid hazards.
Safety Integrity Level (ASIL)(asil, automotive safety integrity level): A risk classification scheme in ISO 26262 that influences the choice of fault injection test objectives.
Safety Lifecycle(safety lifecycle): A structured process covering management, development, production, operation, service, and decommissioning of safety-related systems.
Safety requirements verification: The purpose of test techniques in ISO 26262 to ensure safety requirements are correctly implemented.
Safety-Critical Systems(safety-critical systems): Systems where failure can cause harm, and standards like ISO 26262 recommend back-to-back testing for verification.
Scope Creep: Uncontrolled expansion of project scope due to unmanaged divergent objectives or changing requirements.
Severity, Exposure, Controllability(s, e, c, severity exposure controllability): The three parameters used to determine the ASIL of a hazard.
Software-in-the-Loop(sil, sil): A testing method where production code runs on a simulated hardware platform to verify software behavior before physical hardware is available.
Software-in-the-Loop (SiL)(sil, software-in-the-loop, sil testing): A test method that runs production code in a simulated environment for software integration tests without target hardware.
Software-in-the-Loop Testing(software-in-the-loop, sil, sil testing): A testing method running production code on a simulated hardware platform to enable early verification before physical hardware is available.
State transition testing(state transition testing): A test design technique that uses state transition diagrams to derive test cases for state-dependent behavior.
Static Analysis(static code analysis): A technique that examines code without executing it to find errors and improve quality.
Static Requirements-Based Testing(static requirements-based testing, static rbt): A form of RBT that reviews requirement artifacts without executing software, using techniques like inspections and static analysis.
Static behavior verification(static test): Testing that checks system response under fixed, non-changing input conditions.
System-Level Fault Injection(system-level fault injection): Fault injection applied to the entire vehicle network or system.
Systematic test technique(test technique): A method for deriving test cases from requirements, as defined in the ISTQB glossary.

T

Target Version(target version): The software under test whose outputs are compared against the reference version in back-to-back testing.
Test Environment(mil, sil, hil): A setup used for testing, such as Model-in-the-Loop (MIL), Software-in-the-Loop (SIL), or Hardware-in-the-Loop (HIL).
Test Level Selection(test level selection): The process of choosing the appropriate test level (e.g., unit, integration) based on factors like technique and ASIL.
Test level(test levels): The stage of testing (e.g., unit, integration) that influences test technique selection.
Test technique selection documentation(documentation of test technique selection, documentation of technique selection): Requirement in ISO 26262 to document and justify the selection of test techniques per ASIL.
Test technique selection matrix(matrix mapping safety requirements to techniques): A traceability matrix that maps each safety requirement to a recommended test technique from standards.
Tolerance threshold: The acceptable deviation limit between model and code outputs in back-to-back testing.
Traceability Matrix(traceability matrix): A tool that ensures every requirement is covered by at least one test case or static check.
Traceability matrix for safety requirements(matrix): A matrix mapping each safety requirement to a recommended test technique for compliance.
Traceability to Requirements(requirements traceability): The ability to link test cases to specific requirements to ensure coverage and manage complexity.
Transient Fault(transient fault): A temporary fault such as a bit flip that occurs and then disappears.

V

V-model(v-model): A development process model emphasizing verification and validation at each stage, commonly used in automotive software development.
Vehicle-in-the-Loop(vil, vehicle-in-the-loop): A testing method that places a real vehicle on a dynamometer and replaces real-world inputs with simulation to test ADAS and similar systems safely.
Vehicle-in-the-Loop (ViL)(vil, vehicle-in-the-loop): A test method that places a complete vehicle in a controlled environment with simulated traffic and scenarios for the highest realism.
Verification and Validation (V&V)(verification and validation, v&v): A structured approach to ensure safety requirements are correctly implemented and the system is safe in its vehicle context.

X

XiL selection criteria(selection criteria, xil method selection): Factors such as development phase, test objective, required fidelity, and safety criticality that determine the appropriate XiL method.
XiL spectrum(xil methods, xil): The range of test methods from pure simulation (MiL) to full vehicle testing (ViL), each with different trade-offs in fidelity, cost, and execution speed.
XiL test strategy(xil test strategy, xil, xil strategy): A comprehensive approach integrating Model-in-the-Loop, Software-in-the-Loop, and Hardware-in-the-Loop testing across the development V-model.