| Type | Structure | Best For |
|---|---|---|
| Subsystem harness | Harness wraps a subsystem; inports/outports wired to sources/sinks | Unit test of a single algorithm subsystem |
| Model Reference harness | Harness replaces parent; MUT is a Model Reference block | Component test; MUT isolated from top-level model |
| Top-model SiL harness | Entire model runs in SiL mode; harness provides inputs | Full-model SiL testing; back-to-back comparison |
| External harness (.slx) | Separate .slx file; connects to MUT via model reference | Reusable harness shared across multiple test suites |
Test Harness Types
Auto-Creating a Test Harness
MATLABcreate_harness.m
% Auto-create test harness for SpeedController subsystem
model = "VehicleEMS";
subsystem = "VehicleEMS/SpeedController";
% Create harness: Simulink Test automatically wires inports/outports
harness = sltest.harness.create(subsystem, ...
"HarnessName", "SpeedController_TestHarness", ...
"SynchronizationMode","SyncOnOpen", ...
"SaveExternally", true, ...
"HarnessOwner", subsystem);
% The harness .slx is saved next to the model
% SpeedController_TestHarness.slx
% Verify harness opens correctly
sltest.harness.open(subsystem, "SpeedController_TestHarness");
% Add test stimuli to harness inports
% (Replace Inport blocks with Signal Builder or From File)
set_param("SpeedController_TestHarness/SpeedRef",
"BlockType", "SignalBuilder");
% Rebuild harness after model changes
sltest.harness.rebuild(subsystem, "SpeedController_TestHarness");Summary
Test harness management is the operational backbone of a sustainable MiL test suite. Harnesses that are tightly coupled to the model (inlined rather than external) break every time the model interface changes; external harnesses with synchronisation mode "SyncOnOpen" update their interface automatically when the model changes. Version control discipline for harness files is equally important: the harness is production test infrastructure and must be versioned alongside the model it tests. The rebuild operation after interface changes is the most common source of test suite failures in real projects -- automating it (running sltest.harness.rebuild in the CI pipeline before executing tests) prevents the "tests fail because harness is stale" category of false failures.
🔬 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.