eclipse-score / eclipse-score/reference_integration

Coverage calculation for C++ and Rust

Offen
#259 6 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@dcalavrezo-qorix arbeitet bereits daran.

Seit 23.7.2026.

bug
Vorherrschende Sprache
Python
Sterne
5
Forks
38
Ø Merge
1 T. 2 Std.
Gemergte PRs (30 T.)
22

Beschreibung

Currently issues with coverage calculation are observed across different Modules. We need a common solution that can be applied and used in reference_integration.

Problem definition

Mutual

  • we need solution that is common and can be reused by everyone
  • we need justifications when coverage != 100%, we need mechanisms to justify etc.
  • tooling should support platform variants, allows justifications only for specific one, etc.
  • tooling should allow easy use to developers and clear information where improvements are needed
  • tooling will require certification but there is no other known alternative that will fulfill all our requirements
  • tool requirements initially defined in https://github.com/eclipse-score/communication/pull/549

C++

  • different frameworks have different statements definition - we need that aligned in SCORE
  • bazel coverage is not 100% reliable
  • PR with suggested changes as reference https://github.com/eclipse-score/communication/pull/549
  • No other alternatives exist for our knowledge right now

Rust

  • currently only line coverage is calculated
  • ferrocene toolchain supports only Linux (QNX UTs don't work)
  • there was a new PR in toolchains to support coverage in QNX @PiotrKorkus to check if that works
    https://github.com/eclipse-score/bazel_cpp_toolchains/pull/62
  • other coverages where quoted to ferrocene. Branch coverage would be possible to get with other open-source solutions

It should be possible to use a common tool for generating coverage for both languages.

Next steps

  • Get QNX coverage working for C++
  • Look into Rust coverage
  • Rust and C++ report should have a combined report

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.