| Metric | Definition | Example: if (A && B) -> action |
|---|---|---|
| Statement | Each executable statement executed once | Execute the action once |
| Branch | Each decision branch (true/false) taken once | Execute with A&&B=true; and once with A&&B=false |
| Condition | Each boolean sub-condition true AND false independently | A=T,B=T; A=F,B=T; A=T,B=F; A=F,B=F |
| MC/DC (Modified Condition/Decision Coverage) | Each condition independently affects the decision | A=T,B=T (action); A=F,B=T (no action) -- A independently shown to matter |
Coverage Metric Types
MC/DC: Why It Is Required for ASIL-D
MC/DC Coverage Example
Decision: if (speed > limit && !fault_active) { apply_brake(); }
Conditions:
C1 = (speed > limit)
C2 = (!fault_active)
MC/DC requires N+1 test cases for N conditions (minimum):
Test 1: C1=T, C2=T -> decision=T (baseline)
Test 2: C1=F, C2=T -> decision=F (C1 independently toggles decision)
Test 3: C1=T, C2=F -> decision=F (C2 independently toggles decision)
3 test cases for 2 conditions (vs 4 for full condition coverage)
Why MC/DC for ASIL-D (ISO 26262 Part 6 Table 10):
- Proves each condition has real effect on safety decision
- Catches masking: C1 always true means C2 never tested independently
- Required for airborne (DO-178C Level A) and ASIL-D automotiveCoverage Tools and Configuration
Bashgcov_coverage.sh
#!/bin/bash
# Generate gcov/lcov coverage report for SiL test run
# Compile with coverage instrumentation
gcc -O0 -g --coverage -fprofile-arcs -ftest-coverage \
-o SpeedController_sil \
SpeedController.c SpeedController_data.c \
Adc_Stub.c Can_Stub.c \
-I include/ -I stubs/
# Run all test cases (coverage data collected in .gcda files)
python3 -m pytest tests/ -v
# Generate lcov coverage data
lcov --capture --directory . \
--output-file coverage.info \
--exclude "*/stubs/*" \
--exclude "*/tests/*"
# Generate HTML report
genhtml coverage.info \
--output-directory coverage_report/ \
--branch-coverage \
--title "SpeedController SiL Coverage"
# Print summary
lcov --summary coverage.info
echo "Report: coverage_report/index.html"ASIL Coverage Targets per ISO 26262
| ASIL | Statement | Branch | MC/DC |
|---|---|---|---|
| QM | Recommended | Recommended | Not required |
| ASIL-A | Required | Recommended | Recommended |
| ASIL-B | Required | Required | Recommended |
| ASIL-C | Required | Required | Recommended |
| ASIL-D | Required | Required | Required |
Summary
MC/DC is the most demanding coverage criterion in automotive software testing because it requires demonstrating that each condition in each safety-critical decision independently affects the outcome. For a complex safety monitor with 5 boolean conditions, this requires at least 6 test cases (N+1 minimum) specifically designed so that each condition toggles the decision independently while all others are held constant. The design of MC/DC test cases is where automated tools like Simulink Design Verifier pay off most -- manually identifying the correct input combinations for complex multi-condition decisions in Stateflow charts is error-prone and time-consuming, while SLDV computes them automatically and adds them to the test suite.
🔬 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.