Use cases

The use cases are modelled as stakeholder requirements of the tool user, a module CI pipeline or a developer on a Linux host. Tool requirements satisfy them.

UC1 One report for C++ and Rust		status: valid security: NO safety: ASIL_B
rationale: Module verification reports need one C0/C1 figure per unit regardless of language. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_backend_select, tool_req__coverage_gcov_html, tool_req__coverage_gcov_merge, tool_req__coverage_merge_no_data, tool_req__coverage_merge_profraw, tool_req__coverage_report_merged_profile, tool_req__coverage_report_outputs, tool_req__coverage_validation_ground_truth
The user shall obtain, from one bazel coverage run, one report with line and branch coverage for the C++ and Rust units of the module.
stkh_req__coverage__uc_unified_report		Stakeholder Requirement

UC2 Untested code is visible		status: valid security: NO safety: ASIL_B
rationale: A file no test executes must not disappear from the evidence; it must count with 0 %. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_gcov_baseline, tool_req__coverage_instrumentation_hint, tool_req__coverage_report_allowlist, tool_req__coverage_report_baseline_zero, tool_req__coverage_report_missing_baseline, tool_req__coverage_report_rlib_expansion, tool_req__coverage_report_unmapped, tool_req__coverage_scope_baseline_objects, tool_req__coverage_scope_excludes, tool_req__coverage_scope_gcno, tool_req__coverage_scope_transitive, tool_req__coverage_validation_ground_truth
The user shall see every source file of the declared coverage scope in the report, including files that no test links against, with exact 0 % line and branch coverage for those.
stkh_req__coverage__uc_scope_completeness		Stakeholder Requirement

UC3 Reviewed justifications		status: valid security: NO safety: ASIL_B
rationale: Intentionally uncovered code needs a written, reviewable argument instead of a lowered threshold. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_eff_branch_only, tool_req__coverage_eff_gcovr, tool_req__coverage_eff_html, tool_req__coverage_eff_metric, tool_req__coverage_eff_path_match, tool_req__coverage_eff_stale, tool_req__coverage_just_markers, tool_req__coverage_just_missing_file, tool_req__coverage_just_platform, tool_req__coverage_just_unknown_id, tool_req__coverage_just_yaml
The user shall be able to justify intentionally uncovered lines with a reviewed argument, and obtain an effective coverage figure that counts justified lines as covered while reporting the raw figure alongside.
stkh_req__coverage__uc_justifications		Stakeholder Requirement

UC4 CI gate		status: valid security: NO safety: ASIL_B
rationale: The platform quality criteria (85 % QM, 100 % safety) are enforced automatically. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_gate_exit_codes, tool_req__coverage_gate_metric, tool_req__coverage_gate_no_verdict, tool_req__coverage_gate_threshold, tool_req__coverage_gate_unrounded, tool_req__coverage_merge_tool_error
The user shall be able to fail a CI job when the gated coverage is below a configured threshold, and shall be able to tell a failed gate from a run that could not be evaluated.
stkh_req__coverage__uc_gate		Stakeholder Requirement

UC5 Archived evidence		status: valid security: NO safety: ASIL_B
rationale: The module verification report cites the archived LCOV and justification report. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_artifacts, tool_req__coverage_report_relative_paths
The user shall be able to archive the HTML report, the LCOV data, the justification report and the JUnit results of a run as one CI artifact.
stkh_req__coverage__uc_archive		Stakeholder Requirement

UC6 Job summary		status: valid security: NO safety: QM
rationale: Reviewers read the numbers on the workflow page without downloading artifacts. reqtype: Functional valid_from: v0.1.0 version: 1 satisfied by: tool_req__coverage_summary_first
The user shall obtain a markdown summary of the run, on the GitHub Actions step summary or in a file, even when the gate fails.
stkh_req__coverage__uc_summary		Stakeholder Requirement