Hands-On: Full CI/CD Test Pipeline - Test Automation

Lab: Full CI/CD Test Pipeline

Stage	Tool	Output
1. Lint + validate	Python flake8; config validator	PASS/FAIL; config issues logged
2. Unit tests	pytest --mock	JUnit XML; 0 failures gate
3. SiL smoke tests	pytest --vcan0 in Docker	JUnit XML; HTML report
4. SiL regression	pytest-xdist -n4 in Docker	Full report; traceability matrix
5. Publish artefacts	GitLab artefacts; Grafana push	Dashboard updated; report URL

Exercise 1: GitLab CI YAML

YAML.gitlab-ci.yml

# GitLab CI for ECU test automation pipeline
stages:
  - validate
  - unit_test
  - sil_smoke
  - sil_regression
  - publish

variables:
  DOCKER_IMAGE: "ecu-test-env:latest"

validate_config:
  stage: validate
  script:
    - python3 validate_config.py configs/sil_config.yaml
    - python3 -m flake8 tests/ lib/ --max-line-length=100

unit_tests:
  stage: unit_test
  script:
    - pytest tests/unit/ --junit-xml=reports/unit.xml -q
  artifacts:
    reports:
      junit: reports/unit.xml
    when: always

sil_smoke:
  stage: sil_smoke
  image: $DOCKER_IMAGE
  before_script:
    - modprobe vcan || true
    - ip link add vcan0 type vcan 2>/dev/null || true
    - ip link set vcan0 up
  script:
    - pytest tests/ -m smoke --can-channel=vcan0
          --junit-xml=reports/smoke.xml --tb=short
  artifacts:
    reports:
      junit: reports/smoke.xml
    paths: [reports/]
    when: always

sil_regression:
  stage: sil_regression
  image: $DOCKER_IMAGE
  only: [main, /^release\/.*$/]
  script:
    - pytest tests/ -m "not hil" -n 4
          --can-channel=mock
          --junit-xml=reports/regression.xml
          --html=reports/regression.html
          --self-contained-html
  artifacts:
    reports:
      junit: reports/regression.xml
    paths: [reports/]
    when: always
    expire_in: 30 days

Summary

The full CI/CD pipeline lab brings together all previous topics: the Docker container provides the test environment, the vcan interface enables hardware-free signal testing, pytest-xdist provides parallel execution, and the GitLab artefacts mechanism publishes the JUnit XML and HTML reports automatically. The pipeline structure (validate -> unit -> smoke -> regression) ensures fast feedback on common errors (configuration mistakes fail in 30 seconds; test code errors fail in 2 minutes) while comprehensive regression runs only on the branches that warrant it (main and release). This tiered approach is the industry best practice for automotive CI/CD: developers get fast feedback on every push, and the team gets comprehensive regression results on the builds that count.

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