[AUTO-INF-5] CI: Coverage threshold is 50%, should be 97% #8089

Closed
opened 2026-04-13 03:29:29 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message: fix(ci): raise coverage threshold from 50% to 97% in ci.yml
  • Branch name: fix/ci-quality-gates/coverage-threshold-97

Background and Context

The coverage job in the CI pipeline currently enforces a coverage threshold of 50%. This is significantly lower than the project's stated goal of 97%, which is enforced in the nightly-quality.yml workflow and required by every active milestone's acceptance criteria.

This discrepancy allows code with low test coverage to be merged, potentially introducing bugs and reducing code quality. The CI pipeline should enforce the same high standard as the nightly quality check.

The current implementation has a comment mentioning issues #4183 and #4184, but these issues are closed and the threshold should be updated. This issue is a child of the CI Quality Gates Restoration Epic (#2810), which requires all 11 CI jobs — including coverage — to pass on master with no quality gate suppression or bypasses.

Expected Behavior

The Surface coverage summary step in ci.yml enforces a 97% coverage threshold, consistent with:

  • The nightly-quality.yml workflow threshold
  • All active milestone acceptance criteria (Test coverage >= 97%)
  • The Definition of Done in Epic #2810

The CI coverage job fails if total test coverage drops below 97%, blocking merges that would regress coverage.

Acceptance Criteria

  • The Surface coverage summary step in ci.yml sets threshold = 97
  • The CI coverage job fails when total coverage is below 97%
  • The CI coverage job passes when total coverage is at or above 97%
  • No references to the old 50% threshold remain in ci.yml
  • The change is verified on a branch where coverage is known to be >= 97%
  • The status-check consolidation gate continues to pass after this change

Subtasks

  • Locate the Surface coverage summary step in .github/workflows/ci.yml (or equivalent CI config path)
  • Update threshold = 50threshold = 97 in the inline Python script
  • Remove or update any comments referencing the old threshold or closed issues #4183/#4184
  • Open a PR targeting master with the branch fix/ci-quality-gates/coverage-threshold-97
  • Verify the CI coverage job passes on the PR branch
  • Confirm status-check consolidation gate reports SUCCESS after merge

Definition of Done

This issue is closed when:

  • The coverage job in ci.yml enforces a 97% threshold
  • The CI pipeline passes on master with the new threshold
  • No quality gate is suppressed, bypassed, or weakened
  • The change is merged to master via a reviewed PR

Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message**: `fix(ci): raise coverage threshold from 50% to 97% in ci.yml` - **Branch name**: `fix/ci-quality-gates/coverage-threshold-97` ## Background and Context The `coverage` job in the CI pipeline currently enforces a coverage threshold of **50%**. This is significantly lower than the project's stated goal of **97%**, which is enforced in the `nightly-quality.yml` workflow and required by every active milestone's acceptance criteria. This discrepancy allows code with low test coverage to be merged, potentially introducing bugs and reducing code quality. The CI pipeline should enforce the same high standard as the nightly quality check. The current implementation has a comment mentioning issues #4183 and #4184, but these issues are closed and the threshold should be updated. This issue is a child of the CI Quality Gates Restoration Epic (#2810), which requires all 11 CI jobs — including `coverage` — to pass on `master` with no quality gate suppression or bypasses. ## Expected Behavior The `Surface coverage summary` step in `ci.yml` enforces a **97%** coverage threshold, consistent with: - The `nightly-quality.yml` workflow threshold - All active milestone acceptance criteria (`Test coverage >= 97%`) - The Definition of Done in Epic #2810 The CI `coverage` job fails if total test coverage drops below 97%, blocking merges that would regress coverage. ## Acceptance Criteria - [ ] The `Surface coverage summary` step in `ci.yml` sets `threshold = 97` - [ ] The CI `coverage` job fails when total coverage is below 97% - [ ] The CI `coverage` job passes when total coverage is at or above 97% - [ ] No references to the old 50% threshold remain in `ci.yml` - [ ] The change is verified on a branch where coverage is known to be >= 97% - [ ] The `status-check` consolidation gate continues to pass after this change ## Subtasks - [ ] Locate the `Surface coverage summary` step in `.github/workflows/ci.yml` (or equivalent CI config path) - [ ] Update `threshold = 50` → `threshold = 97` in the inline Python script - [ ] Remove or update any comments referencing the old threshold or closed issues #4183/#4184 - [ ] Open a PR targeting `master` with the branch `fix/ci-quality-gates/coverage-threshold-97` - [ ] Verify the CI `coverage` job passes on the PR branch - [ ] Confirm `status-check` consolidation gate reports SUCCESS after merge ## Definition of Done This issue is closed when: - The `coverage` job in `ci.yml` enforces a 97% threshold - The CI pipeline passes on `master` with the new threshold - No quality gate is suppressed, bypassed, or weakened - The change is merged to `master` via a reviewed PR --- **Automated by CleverAgents Bot** Agent: new-issue-creator
HAL9000 added this to the v3.5.0 milestone 2026-04-13 03:29:36 +00:00
Owner

superseded by next cycle

superseded by next cycle
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8089
No description provided.