Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Pytest Parametrize for Signal Tests

Pythontest_aeb_parametrized.py
"""Parametrized AEB tests: same test logic, different signal values."""
import pytest

AEB_TEST_CASES = [
    # (speed_kmh, radar_dist_m, expected_aeb_state, expected_brake_min)
    (10,  40,  "INACTIVE",  0),    # too slow for AEB
    (50,  40,  "ACTIVE",   30),    # normal AEB activation
    (80,  35,  "ACTIVE",   60),    # higher speed = more braking
    (120, 30,  "ACTIVE",   90),    # highway AEB
    (200, 40,  "ACTIVE",   30),    # above ODD - AEB may not activate
    (50,  100, "INACTIVE",  0),    # target too far
    (50,   5,  "ACTIVE",  100),    # imminent collision
]

@pytest.mark.parametrize(
    "speed, radar_dist, expected_state, expected_brake_min",
    AEB_TEST_CASES,
    ids=[f"speed{t[0]}_dist{t[1]}" for t in AEB_TEST_CASES]
)
def test_aeb_response(ecu, speed, radar_dist,
                       expected_state, expected_brake_min):
    ecu.send_signal("VehicleSpeed", speed)
    ecu.send_signal("RadarTarget_Distance", radar_dist)
    import time; time.sleep(0.3)
    state = ecu.read_signal("AEB_State", timeout_s=0.5)
    assert state == expected_state, f"AEB state {state} != {expected_state}"
    if expected_brake_min > 0:
        brake = ecu.read_signal("AEB_BrakeRequest_pct", timeout_s=0.5)
        assert brake >= expected_brake_min, f"Brake {brake} < {expected_brake_min}"

CSV-Driven Test Data

Pythontest_from_csv.py
"""Load test parameters from CSV for data-driven testing."""
import pytest, csv
from pathlib import Path

def load_test_vectors(csv_path: str):
    """Load test vectors from CSV; first row is headers."""
    rows = []
    with open(csv_path) as f:
        reader = csv.DictReader(f)
        for row in reader:
            if not row.get("skip", "").lower() == "true":
                rows.append({
                    "speed": float(row["speed_kmh"]),
                    "dist":  float(row["radar_dist_m"]),
                    "exp_state": row["expected_aeb_state"],
                    "exp_brake":  float(row["expected_brake_min_pct"]),
                    "req_id":     row["req_id"],
                    "tc_id":      row["tc_id"],
                })
    return rows

TEST_VECTORS = load_test_vectors("test_data/aeb_vectors.csv")

@pytest.mark.parametrize("vec", TEST_VECTORS,
                          ids=[v["tc_id"] for v in TEST_VECTORS])
def test_aeb_csv_driven(ecu, vec):
    ecu.send_signal("VehicleSpeed", vec["speed"])
    ecu.send_signal("RadarTarget_Distance", vec["dist"])
    import time; time.sleep(0.3)
    state = ecu.read_signal("AEB_State", timeout_s=0.5)
    assert state == vec["exp_state"]

Summary

Data-driven testing with CSV files creates a clean separation between test logic (Python) and test data (spreadsheet/CSV). This separation has a significant benefit in automotive validation: the test data (expected values for each signal combination) is the responsibility of the system engineer or validation team who understands the requirements, while the test logic is the responsibility of the test automation engineer. When requirements change (the AEB activation threshold changes from 40m to 35m), the system engineer updates the CSV file without touching Python code. The CSV format also enables non-programmers to add test cases and enables the requirement ID (req_id column) to be embedded directly in the test data for ASPICE traceability.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSignal-Based and Bus-Based TestingNext →Report Generation and Analysis