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

Test Report Types and Purposes

Report TypeFormatConsumerContent
JUnit XMLXMLCI/CD (Jenkins/GitLab)Pass/fail counts; duration; failure message
HTML reportHTMLTest engineer; managerVisual pass/fail; charts; screenshots
ASPICE evidencePDF/ExcelAssessor; quality managerReq traceability; verdict; reviewer sign-off
Coverage reportHTML/XMLSW developer; auditorLine/branch/MC/DC coverage per module
Trend reportHTML/dashboardProject managerPass rate over time; flaky test detection

Generating JUnit XML with pytest

Bashrun_tests.sh
#!/bin/bash
# Run test suite with JUnit XML output for Jenkins/GitLab
pytest tests/ \
    --junit-xml=test_results/report.xml \
    --html=test_results/report.html \
    --self-contained-html \
    --tb=short \
    --log-cli-level=INFO \
    --log-file=test_results/test.log \
    -v \
    --can-channel=vcan0 \
    --dbc=vehicle.dbc \
    -m "not hil"  # skip HiL tests in CI

# Parse results
python3 << EOF
import xml.etree.ElementTree as ET
tree = ET.parse("test_results/report.xml")
root = tree.getroot()
suite = root.find("testsuite") or root
print(f"Tests: {suite.get('tests')} "
      f"Passed: {int(suite.get('tests',0))-int(suite.get('failures',0))-int(suite.get('errors',0))} "
      f"Failed: {suite.get('failures')} "
      f"Errors: {suite.get('errors')}")
EOF

Traceability Matrix Report Generator

Pythongen_traceability_report.py
"""Generate ASPICE-compliant requirements traceability matrix."""
import xml.etree.ElementTree as ET
import csv
from collections import defaultdict

def build_traceability_matrix(junit_xml: str, req_csv: str) -> dict:
    """Link test results to requirements via test IDs."""
    # Load requirements
    reqs = {}
    with open(req_csv) as f:
        for row in csv.DictReader(f):
            reqs[row["req_id"]] = row
    # Load test results
    tree = ET.parse(junit_xml)
    results = {}
    for tc in tree.iter("testcase"):
        tc_id = tc.get("name")
        verdict = "FAIL" if tc.find("failure") is not None else "PASS"
        results[tc_id] = verdict
    # Build matrix
    matrix = defaultdict(list)
    for tc_id, verdict in results.items():
        req_id = tc_id.split("_")[1] if "_" in tc_id else "UNKNOWN"
        matrix[req_id].append({"tc_id": tc_id, "verdict": verdict})
    uncovered = [r for r in reqs if r not in matrix]
    return {"matrix": dict(matrix), "uncovered_reqs": uncovered}

Summary

Test reporting serves three different audiences with different needs. The JUnit XML format serves the CI/CD pipeline: Jenkins and GitLab parse it to determine whether the build passes and to track trends over time. The HTML report serves the test engineer: it shows which tests failed, what the actual vs expected values were, and the log output that helps diagnose root causes. The ASPICE evidence report serves the assessor and quality manager: it must show which requirements were tested, what the verdict was, who reviewed the test cases, and when the tests were run. Automating all three from the same test execution (--junit-xml, --html, and a custom traceability report generator) ensures they are consistent and eliminates the manual effort of creating evidence documents.

🔬 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.

← PreviousParameterised and Data-Driven TestsNext →Hands-On: Complete ECU Test Project