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

Lab: Coverage Gap Analysis

StepActivityOutput
1Run test suite; collect coverage reportCoverage HTML with red (uncovered) blocks
2Classify each gap: missing test or justified exclusionGap classification spreadsheet
3Run SLDV on gaps classified as "missing test"New test cases in .mldatx
4Document justified exclusionsExclusion register with safety manager approval
5Rerun; verify 100% branch and 90%+ MC/DCUpdated coverage report

Exercise 1: Gap Classification Script

Pythonclassify_gaps.py
"""Parse lcov coverage report and classify uncovered lines."""
import subprocess
import re
import json

def parse_lcov_gaps(info_file: str) -> list:
    """Extract uncovered lines from lcov .info file."""
    gaps = []
    current_file = None
    with open(info_file) as f:
        for line in f:
            if line.startswith("SF:"):
                current_file = line[3:].strip()
            elif line.startswith("DA:"):
                # DA:line_number,execution_count
                parts = line[3:].strip().split(",")
                line_no = int(parts[0])
                exec_count = int(parts[1])
                if exec_count == 0 and current_file:
                    # Skip stubs/ and test files
                    if "stubs/" not in current_file \
                    and "test" not in current_file:
                        gaps.append({
                            "file": current_file,
                            "line": line_no,
                            "classified": "unclassified",
                            "action": ""
                        })
    return gaps

gaps = parse_lcov_gaps("coverage.info")
print(f"Uncovered lines: {len(gaps)}")

# Save for manual classification
with open("gap_classification.json", "w") as f:
    json.dump(gaps, f, indent=2)
print("Edit gap_classification.json to classify each gap:")
print("  classified: missing_test | justified_exclusion | equivalent_mutant")
print("  action: add_test_TC_xxx | exclusion_rationale")

Summary

Coverage gap analysis is a structured engineering activity, not a hunt for missing tests. The classification step -- determining whether each gap is a missing test case or a justified exclusion -- is the most important step because it determines the correct resolution. A gap classified as "missing test" requires a new test case; a gap classified as "justified exclusion" requires a documented rationale. The most common mistake is classifying difficult-to-test conditions as "justified exclusions" without proper analysis -- safety assessors are trained to identify this pattern and will request evidence that the condition is genuinely unreachable, not just hard to test. SLDV formal analysis (proving the condition unreachable) is the gold-standard evidence for an exclusion; manual signal flow tracing is acceptable but requires more detailed documentation.

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

← PreviousMutation Testing for Test QualityNext →Continuous Testing Architecture