What problem does it solve?
Engineers reviewing Simulink Coverage results often cannot tell whether an uncovered decision, condition, MCDC, relational-boundary, or saturation outcome is provably dead logic, an untested reachable path, or intentional defensive design. This Skill analyzes an existing coverage result and explains why each objective is missing, separating formal facts from engineering judgment.
Core Features & Use Cases
- Coverage summarization: Reads an existing cvdata, .cvt file, sim-with-coverage output, or Simulink Test result and reports satisfied versus unsatisfied objectives per system, worst-first.
- Dead-logic detection: Runs Simulink Design Verifier dead-logic analysis on decision, condition, and MCDC outcomes and joins verdicts to coverage outcomes deterministically, distinguishing provably dead from reachable-but-untested.
- Root-cause tracing: Uses Model Slicer to trace each uncovered outcome to its controllable inputs and dependency chain, then recommends a test scenario, a coverage filter (Justify mode), or a design review.
- Use Case: After running coverage on a controller model, ask why specific MCDC outcomes are uncovered; the Skill proves which are dead logic, traces the rest to their driving inports, and proposes the exact input conditions a new test must drive.
Quick Start
Ask the agent to explain why coverage objectives are missing in my existing coverage result file results.cvt and recommend how to close each gap.
