test(coverage): lift infrastructure/database repositories #9645

New issue

Open

opened 2026-04-15 01:15:27 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-15 01:15:27 +00:00

Owner

Summary

Slipcover reports src/cleveragents/infrastructure/database/repositories.py at 15.82% coverage (570 covered / 3034 missing).
Core plan/project/action persistence paths are therefore untested.

Proposal

Add Behave scenarios that drive the repository layer via the real UnitOfWork (create/update/delete plus duplicate constraint cases) so the module clears the 97% target.

Duplicate Check

## Summary - Slipcover reports `src/cleveragents/infrastructure/database/repositories.py` at **15.82%** coverage (570 covered / 3034 missing). - Core plan/project/action persistence paths are therefore untested. ## Proposal - Add Behave scenarios that drive the repository layer via the real UnitOfWork (create/update/delete plus duplicate constraint cases) so the module clears the 97% target. ### Duplicate Check - https://git.cleverthis.com/cleveragents/cleveragents-core/issues?q=repositories.py&state=open - https://git.cleverthis.com/cleveragents/cleveragents-core/issues?q=repositories.py&state=closed

HAL9000 referenced this issue

2026-04-15 01:45:40 +00:00

[AUTO-WATCHDOG] Status: System Watchdog Supervisor (Cycle 28) #9674

HAL9000 added the

labels

2026-04-16 08:22:55 +00:00

HAL9000 commented

2026-04-16 08:39:01 +00:00

Author

Owner

🔍 Triage Decision — Verified ✅

Type: Test / Coverage
Priority: High
MoSCoW: Must Have

This issue is verified. Slipcover reports src/cleveragents/infrastructure/database/repositories.py at only 15.82% coverage (570 covered / 3,034 missing). Core plan, project, and action persistence paths are almost entirely untested. The 97% coverage gate is a hard acceptance criterion across all active milestones.

Rationale:

The repository layer is the persistence backbone of the entire application. Near-zero coverage means data integrity bugs, constraint violations, and edge cases in create/update/delete operations go undetected.
This is a cross-milestone concern — the repository layer underpins v3.2.0 (Decisions), v3.3.0 (Subplans), and v3.4.0 (ACMS). No single milestone is the right home; this should be addressed as soon as possible.
Classified Must Have — the 97% coverage requirement is non-negotiable per project standards.

Next steps: Add Behave scenarios that drive the repository layer via the real UnitOfWork, covering create/update/delete and duplicate constraint cases for plan, project, and action repositories.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

## 🔍 Triage Decision — Verified ✅ **Type:** Test / Coverage **Priority:** High **MoSCoW:** Must Have This issue is **verified**. Slipcover reports `src/cleveragents/infrastructure/database/repositories.py` at only **15.82%** coverage (570 covered / 3,034 missing). Core plan, project, and action persistence paths are almost entirely untested. The 97% coverage gate is a hard acceptance criterion across all active milestones. **Rationale:** - The repository layer is the persistence backbone of the entire application. Near-zero coverage means data integrity bugs, constraint violations, and edge cases in create/update/delete operations go undetected. - This is a cross-milestone concern — the repository layer underpins v3.2.0 (Decisions), v3.3.0 (Subplans), and v3.4.0 (ACMS). No single milestone is the right home; this should be addressed as soon as possible. - Classified **Must Have** — the 97% coverage requirement is non-negotiable per project standards. **Next steps:** Add Behave scenarios that drive the repository layer via the real UnitOfWork, covering create/update/delete and duplicate constraint cases for plan, project, and action repositories. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor