What
Reach 90% line coverage and 90% branch coverage for the score/TimeSlave/
component once its implementation is available (see epic
eclipse-score/score#2691).
Steps:
- Generate a per-component coverage report locally:
bazel coverage --config=time-x86_64-linux //score/TimeSlave/...
genhtml --branch-coverage bazel-out/_coverage/_coverage_report.dat -o coverage-report/
- Identify files and branches below 90%
- Add missing unit tests — focus areas:
- IPC channel (libTSClient) — connection, disconnection, error paths
- PTP sync loop — synchronization state transitions
clock_adjtime / clock_settime integration — stub/mock the syscall
- TimeSlave process lifecycle — start, stop, restart
References
Depends on
TimeSlave implementation (eclipse-score/score#2691) must be sufficiently
complete before this task can begin.
Estimates for realization
M - Week
Category
Requirements / Architecture
What
Reach 90% line coverage and 90% branch coverage for the
score/TimeSlave/component once its implementation is available (see epic
eclipse-score/score#2691).
Steps:
clock_adjtime/clock_settimeintegration — stub/mock the syscallReferences
https://github.com/eclipse-score/score/blob/main/docs/contribute/development/cpp/code_analysis.rst
Depends on
TimeSlave implementation (eclipse-score/score#2691) must be sufficiently
complete before this task can begin.
Estimates for realization
M - Week
Category
Requirements / Architecture