ASPICE-Compliant Test Documentation - Test Automation

ASPICE SWE.4 and SWE.6 Test Requirements

ASPICE BP	Requirement	Test Automation Implementation
SWE.4 BP1	Test cases defined and documented	Test cases in version-controlled files with req_id attribute
SWE.4 BP2	Test cases traceable to requirements	pytest marker @pytest.mark.req(); traceability matrix report
SWE.4 BP3	Regression test suite maintained	All passing tests retained; CI runs regression on every merge
SWE.6 BP1	Software unit tested	Unit test suite with pytest; coverage report (MC/DC for ASIL-B+)
SWE.6 BP2	Test results documented	JUnit XML + HTML report; auto-generated ASPICE evidence PDF
SWE.6 BP4	Consistent with requirements	Traceability matrix shows 100% req coverage; no orphaned tests

ASPICE Test Specification Header

YAMLtest_specification.yaml

# ASPICE SWE.4/SWE.6 Test Specification
document:
  title: "AEB ECU Software Test Specification"
  doc_id: "TST-AEB-001"
  version: "2.1"
  status: "Approved"
  author: "validation.team@tier1.com"
  reviewer: "qa.manager@tier1.com"
  approval_date: "2025-02-10"

scope:
  ecu: "AEB_ECU v4.2.0"
  sw_requirements_doc: "SRS-AEB-v3.4"
  test_environment: "HiL_SCALEXIO + Vector VN1640"

test_items:
  - id: TC-AEB-001
    title: "AEB activation at 50 km/h with 40m target"
    requirement: SWR-AEB-001
    asil: ASIL-B
    test_level: HiL
    automation_status: Automated
    script: "tests/test_aeb.py::test_aeb_response[speed50_dist40]"
    precondition: "ECU in normal mode; no active DTCs; speed=0"
    stimulus: "VehicleSpeed=50.0; RadarTarget_Distance=40.0"
    expected_result: "AEB_State=ACTIVE within 200ms; BrakeRequest>=30%"
    verdict_criteria: "Both checks pass within tolerance"

Evidence Package Assembly

Pythonassemble_evidence.py

"""Assemble ASPICE test evidence package."""
import os, shutil, json
from datetime import datetime

def assemble_evidence_package(
        test_results_dir: str,
        output_dir: str,
        release_version: str) -> str:
    ts = datetime.now().strftime("%Y%m%d_%H%M%S")
    pkg_dir = os.path.join(output_dir,
                           f"aspice_evidence_{release_version}_{ts}")
    os.makedirs(pkg_dir, exist_ok=True)

    # 01 Test specification
    shutil.copy("test_specification.yaml",
                os.path.join(pkg_dir, "01_test_specification.yaml"))

    # 02 Test results (JUnit XML)
    for xml in [f for f in os.listdir(test_results_dir) if f.endswith(".xml")]:
        shutil.copy(os.path.join(test_results_dir, xml),
                    os.path.join(pkg_dir, f"02_{xml}"))

    # 03 HTML report
    for html in [f for f in os.listdir(test_results_dir) if f.endswith(".html")]:
        shutil.copy(os.path.join(test_results_dir, html),
                    os.path.join(pkg_dir, f"03_{html}"))

    # 04 Traceability matrix
    shutil.copy("reports/traceability_matrix.html",
                os.path.join(pkg_dir, "04_traceability_matrix.html"))

    # 05 Package manifest
    manifest = {
        "release": release_version,
        "timestamp": ts,
        "contents": os.listdir(pkg_dir)
    }
    with open(os.path.join(pkg_dir, "00_manifest.json"), "w") as f:
        json.dump(manifest, f, indent=2)

    return pkg_dir

Summary

ASPICE-compliant test documentation is the output that transforms automated test results from internal engineering evidence into externally auditable quality records. The evidence package must be self-contained: an ASPICE assessor who has never seen the project should be able to open the package and answer "what was tested, how was it tested, what were the results, and what requirements does this evidence cover?" without asking the team. The automated evidence assembly script is the final piece of the automation puzzle: it converts raw test outputs (JUnit XML, HTML reports, traceability CSV) into a structured evidence package that meets the ASPICE documentation requirements. With this assembly automated, every CI/CD regression run produces ASPICE-compliant evidence with zero 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.