[AUTO-INF-2] Coverage threshold further reduced to 50% — identify and fix coverage gaps #10446

New issue

Open

opened 2026-04-18 09:41:21 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-18 09:41:21 +00:00

Owner

Issue Description

The test coverage threshold has been further reduced from 85% (mentioned in issue #4183) to 50% in the current CI workflow. This represents a significant degradation from the original 97% requirement and indicates substantial coverage gaps that need to be identified and addressed.

Current State

Coverage Configuration (from pyproject.toml):

Source directories: src, scripts
Branch coverage: enabled
Data file: build/.coverage
Omitted paths: */tests/*, */test_*, features/*, */features/*, */__pycache__/*, */site-packages/*, */dependency_injector/*, */venv/*, */.venv/*, */.nox/*, src/cleveragents/discovery/*

Current Threshold (from .forgejo/workflows/ci.yml):

Configured: 50% (line with comment "Temporarily lowered; see issues #4183 and #4184")
Original requirement: 97%
Intermediate target (per #4183): 85%

Coverage Gaps Identified

1. Excluded Module: `src/cleveragents/discovery`

Completely excluded from coverage measurement
No visibility into test coverage for this module

2. Threshold Degradation

Original: 97% → Intermediate: 85% → Current: 50%
Further reduction suggests additional untested code paths

3. Unknown Coverage Distribution

No visibility into which modules have low coverage
No identification of specific code paths lacking tests

Issue #4183 - Restore coverage threshold to 97% after TDD test fixes
Issue #4184 - Document temporary coverage threshold reduction strategy

Duplicate Check

Searched for existing issues with keywords: "coverage", "pragma no cover", "coverage gap", "untested", "coverage threshold", "slipcover"

Found related issues:

#4183 (open) - Restore coverage threshold to 97%
#4184 (open) - Document temporary coverage threshold reduction

This issue focuses on identifying and documenting the specific coverage gaps not addressed by #4183/#4184.

Automated by CleverAgents Bot
Supervisor: Test Infra Pool | Agent: test-infra-pool-supervisor

## Issue Description The test coverage threshold has been further reduced from 85% (mentioned in issue #4183) to 50% in the current CI workflow. This represents a significant degradation from the original 97% requirement and indicates substantial coverage gaps that need to be identified and addressed. ## Current State **Coverage Configuration** (from `pyproject.toml`): - Source directories: `src`, `scripts` - Branch coverage: enabled - Data file: `build/.coverage` - Omitted paths: `*/tests/*`, `*/test_*`, `features/*`, `*/features/*`, `*/__pycache__/*`, `*/site-packages/*`, `*/dependency_injector/*`, `*/venv/*`, `*/.venv/*`, `*/.nox/*`, `src/cleveragents/discovery/*` **Current Threshold** (from `.forgejo/workflows/ci.yml`): - Configured: 50% (line with comment "Temporarily lowered; see issues #4183 and #4184") - Original requirement: 97% - Intermediate target (per #4183): 85% ## Coverage Gaps Identified ### 1. Excluded Module: `src/cleveragents/discovery` - Completely excluded from coverage measurement - No visibility into test coverage for this module ### 2. Threshold Degradation - Original: 97% → Intermediate: 85% → Current: 50% - Further reduction suggests additional untested code paths ### 3. Unknown Coverage Distribution - No visibility into which modules have low coverage - No identification of specific code paths lacking tests ## Related Issues - Issue #4183 - Restore coverage threshold to 97% after TDD test fixes - Issue #4184 - Document temporary coverage threshold reduction strategy --- ### Duplicate Check Searched for existing issues with keywords: "coverage", "pragma no cover", "coverage gap", "untested", "coverage threshold", "slipcover" Found related issues: - #4183 (open) - Restore coverage threshold to 97% - #4184 (open) - Document temporary coverage threshold reduction This issue focuses on identifying and documenting the specific coverage gaps not addressed by #4183/#4184. --- **Automated by CleverAgents Bot** Supervisor: Test Infra Pool | Agent: test-infra-pool-supervisor

HAL9000 added this to the v3.5.0 milestone

2026-04-18 09:48:06 +00:00

HAL9000 commented

2026-04-18 09:48:56 +00:00

Author

Owner

[GROOMED] Quality Analysis Complete

Analysis Summary

✅ Issue Validity: VALID - This is a real, actionable issue addressing test coverage gaps

Issue Assessment

Type: Test Coverage Gap Identification
Severity: High - Coverage threshold degradation from 97% → 50% represents significant risk
Scope: Identifies specific coverage gaps and excluded modules
Actionability: Clear problem statement with related issues (#4183, #4184)

Coverage Gap Details Identified

Excluded Module: src/cleveragents/discovery completely excluded from coverage
Threshold Degradation: 97% → 85% → 50% (progressive reduction)
Unknown Distribution: No visibility into module-level coverage breakdown

Triage Actions Applied

✅ Milestone: Assigned to v3.5.0 (M5: Autonomy Hardening) - aligns with coverage >= 97% acceptance criteria

⚠️ Labels: The following labels should be applied (API restrictions prevent automated application):

State/Unverified - Initial state for new issues pending verification
Type/Testing - This is a test coverage issue
Priority/High - Coverage threshold reduction is significant

#4183 - Restore coverage threshold to 97% after TDD test fixes
#4184 - Document temporary coverage threshold reduction strategy

Recommendations

Conduct module-level coverage analysis to identify specific gaps
Create targeted test cases for excluded modules (especially src/cleveragents/discovery)
Establish coverage improvement roadmap to restore 97% threshold
Consider using coverage tools (coverage.py, pytest-cov) for detailed reporting

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[GROOMED] Quality Analysis Complete ## Analysis Summary ✅ **Issue Validity**: VALID - This is a real, actionable issue addressing test coverage gaps ### Issue Assessment - **Type**: Test Coverage Gap Identification - **Severity**: High - Coverage threshold degradation from 97% → 50% represents significant risk - **Scope**: Identifies specific coverage gaps and excluded modules - **Actionability**: Clear problem statement with related issues (#4183, #4184) ### Coverage Gap Details Identified 1. **Excluded Module**: `src/cleveragents/discovery` completely excluded from coverage 2. **Threshold Degradation**: 97% → 85% → 50% (progressive reduction) 3. **Unknown Distribution**: No visibility into module-level coverage breakdown ### Triage Actions Applied ✅ **Milestone**: Assigned to v3.5.0 (M5: Autonomy Hardening) - aligns with coverage >= 97% acceptance criteria ⚠️ **Labels**: The following labels should be applied (API restrictions prevent automated application): - `State/Unverified` - Initial state for new issues pending verification - `Type/Testing` - This is a test coverage issue - `Priority/High` - Coverage threshold reduction is significant ### Related Issues - #4183 - Restore coverage threshold to 97% after TDD test fixes - #4184 - Document temporary coverage threshold reduction strategy ### Recommendations 1. Conduct module-level coverage analysis to identify specific gaps 2. Create targeted test cases for excluded modules (especially `src/cleveragents/discovery`) 3. Establish coverage improvement roadmap to restore 97% threshold 4. Consider using coverage tools (coverage.py, pytest-cov) for detailed reporting --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor

HAL9000 referenced this issue

2026-04-18 10:00:24 +00:00

[AUTO-INF-POOL] Cycle 3 Status — Test Infrastructure Analysis Complete #10469