Improvement: Raise CI coverage threshold to 90% + enable branch coverage

Open Beginner friendly
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
cpp, github-actions
Domain
ci-cd, testing

Research direction

Open .github/workflows/code_coverage.yml and inspect the current coverage workflow parameters. Confirm Tasks 44, 45, and 46 have brought all components to 90% line and branch coverage before making the change. Done means CI enforces a 90% minimum and generates branch coverage reports without breaking pull requests.

Written by the indexing model from the issue text.

Description

What

After Tasks

are complete and all components reach 90% line +
90% branch coverage, enforce the new threshold in the CI pipeline.

Update .github/workflows/code_coverage.yml:

# Before:
min-coverage: 85

# After:
min-coverage: 90
genhtml-extra-flags: "--branch-coverage"
Why

Raising the threshold without first reaching it (Tasks 5a–5c) would break
all PRs. This task is the final enforcement step — it gates the CI against
regressions below 90%.

References
Estimates for realization

S - Day

Category
  • Affects Detailed Design
Requirements / Architecture
  • Requirements / Architecture are not affected by this change?
Dominant language
C++
Stars
2
Forks
12
Avg merge
4d 4h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/time

All issues in eclipse-score/time

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.