| ASPICE Process | Key Practices | HIL Artefacts |
|---|---|---|
| SWE.4: Software Unit Verification | Unit test plan; unit test specification; coverage report; unit test results | Unit test suite, MC/DC coverage report |
| SWE.5: SW Integration and Testing | Integration test strategy; integration test specification; integration test results | HIL test cases, CAN trace logs, HIL test reports |
| SWE.6: SW Qualification Testing | System-level functional test of SW against requirements; confirmation measures | Vehicle-level HIL test reports, requirements trace matrix |
| MAN.5: Project Management | Test planning as part of project plan; milestone tracking | Test plan document with milestones and pass/fail criteria |
ASPICE SWE.4 and SWE.5: Software Testing
ISO 26262 Test Evidence Requirements
| ISO 26262 Requirement | Test Evidence Type | Report Content |
|---|---|---|
| Part 6 Clause 9: SW unit testing | Unit test specification + results | Test case ID, requirement ID, pass/fail, coverage % |
| Part 6 Clause 10: SW integration testing | Integration test spec + results | Interface test cases, E2E protection verification, FFI tests |
| Part 5: Hardware metrics validation | Fault injection test report | DC claim, fault injected, detection time, measured DC% |
| Part 4: System validation | HIL validation test report | Safety goal addressed, test method, pass criterion, result |
| Part 9: FMEA validation | DC validation test evidence | Each FMEA diagnostic mechanism validated by test |
HIL Test Report Generator
Pythontest_report_generator.py
#!/usr/bin/env python3
# Generate ASPICE-compliant HTML test report from pytest results
import json, datetime
from pathlib import Path
def generate_hil_report(results_json: str, output_html: str):
with open(results_json) as f:
results = json.load(f)
total = len(results["tests"])
passed = sum(1 for t in results["tests"] if t["outcome"] == "passed")
failed = total - passed
rate = 100 * passed / total if total else 0
html = f"""
<html><head><title>HIL Test Report</title></head><body>
<h1>HIL Integration Test Report</h1>
<p>Generated: {datetime.datetime.now().isoformat()}</p>
<p>ECU SW Build: {results.get("sw_version", "N/A")}</p>
<h2>Summary</h2>
<table border="1">
<tr><th>Total</th><th>Passed</th><th>Failed</th><th>Pass Rate</th></tr>
<tr><td>{total}</td><td>{passed}</td><td>{failed}</td><td>{rate:.1f}%</td></tr>
</table>
<h2>Test Cases</h2><table border="1">
<tr><th>ID</th><th>Requirement</th><th>Result</th><th>Duration</th></tr>
"""
for t in results["tests"]:
color = "green" if t["outcome"] == "passed" else "red"
req = t.get("markers", {}).get("req_id", "-")
html += f'<tr><td>{t["nodeid"]}</td><td>{req}</td>'
html += f'<td style="color:{color}">{t["outcome"].upper()}</td>'
html += f'<td>{t["duration"]:.2f}s</td></tr>'
html += "</table></body></html>"
Path(output_html).write_text(html)
print(f"Report: {output_html} ({passed}/{total} passed)")Summary
Test reports for ASPICE Level 2 and ISO 26262 projects must be traceable, reproducible, and formally reviewed. Every test report must state: which ECU SW version was tested, which test specification version was used, the environment (HIL platform, plant model version, tool versions), and the individual pass/fail result for each test case with its unique ID. An automated report generator that runs as part of the CI pipeline and produces a dated, versioned HTML or PDF report after every test run ensures these requirements are met without manual effort.
🔬 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.