Equivalence Class Testing - SIL/MIL Testing

Equivalence Class Testing for Embedded SW

Why Equivalence Classes?

Exhaustive testing of an automotive speed controller with floating-point inputs is impossible: the input space is continuous and infinite. Equivalence Class Testing (ECT) divides the input space into classes where all values in a class are expected to produce the same type of behaviour -- then tests one representative value per class.

For a speed controller with input range 0-120 km/h:

Valid class: 0-120 km/h (expected: normal control)
Invalid class (low): negative values (expected: fault or clamp to 0)
Invalid class (high): > 120 km/h (expected: speed limit fault)
Boundary class: 0, 120 (boundary values within valid range)

Input Space Partitioning Example

Pythonequivalence_test.py

"""Equivalence class test cases for HVAC temperature controller."""
import pytest

# Input: setpoint_C and cabin_temp_C
# ECT partitions:
#   Setpoint: [invalid_low: < 16], [valid: 16-28], [invalid_high: > 28]
#   Cabin temp: [cold: < 10], [normal: 10-40], [hot: > 40]

ECT_CLASSES = [
    # (test_name, setpoint, cabin_temp, expected_mode, desc)
    # Valid setpoint + normal cabin temp classes
    ("ect_normal_cooling",   22.0, 28.0, "COOLING",   "Valid: hot cabin, needs cooling"),
    ("ect_normal_heating",   22.0, 16.0, "HEATING",   "Valid: cold cabin, needs heating"),
    ("ect_normal_balanced",  22.0, 22.0, "MAINTAIN",  "Valid: cabin at setpoint"),
    # Invalid setpoint classes
    ("ect_invalid_low_sp",   10.0, 22.0, "FAULT",     "Invalid: setpoint below minimum"),
    ("ect_invalid_high_sp",  35.0, 22.0, "FAULT",     "Invalid: setpoint above maximum"),
    # Extreme cabin temperature classes
    ("ect_cold_cabin",       22.0,  5.0, "MAX_HEAT",  "Cold cabin: full heat output"),
    ("ect_hot_cabin",        22.0, 45.0, "MAX_COOL",  "Hot cabin: full cooling output"),
]

@pytest.mark.parametrize("name,setpoint,cabin,expected_mode,desc",
                          ECT_CLASSES,
                          ids=[c[0] for c in ECT_CLASSES])
def test_hvac_ect(name, setpoint, cabin, expected_mode, desc):
    """Run HVAC ECT class representative value."""
    # (Replace with actual SiL call)
    result = run_hvac_sil(setpoint_c=setpoint, cabin_temp_c=cabin)
    assert result["mode"] == expected_mode, \
        f"ECT class [{name}] failed: {desc}"

Summary

Equivalence class testing and boundary value analysis are complementary: ECT reduces the number of test cases needed to cover the input space (test one representative per class, not all values), while BVA ensures that the boundaries between classes are explicitly tested (where bugs concentrate). Together they form the foundation of systematic black-box test design. For automotive embedded software with many input signals, the combination is applied per signal first (univariate ECT), then for the most safety-critical combinations of two or three signals (pairwise or three-way combinatorial testing). This structured approach produces test suites that are both efficient (minimum test cases) and defensible to safety assessors (every class is covered by design, not by chance).

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.