cleveragents/cleveragents-core

Fork 3

TEST-INFRA: [missing-test-levels] Missing Robot tests for acms module #5766

New issue

Open

opened 2026-04-09 09:14:48 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 09:14:48 +00:00

Owner

Metadata

Branch: test-infra/robot-tests-acms
Commit Message: test(acms): add Robot Framework integration tests for the acms module
Milestone: (to be assigned — see backlog note below)
Parent Epic: #5407

Overview

The acms module (Advanced Context Management System) has several Robot Framework test files covering the pipeline, backends, and fusion layers (acms_pipeline.robot, acms_backends.robot, acms_fusion.robot, etc.), but integration-level coverage is incomplete. Key sub-components — including the UKO vocabulary layer (src/cleveragents/acms/uko/), scope resolution (scope_resolution.py), ontology registry (ontology_registry.py), temporal models (temporal.py), CRP (crp.py), and the various language analyzers (python_analyzer.py, markdown_analyzer.py, docker_compose_analyzer.py, postgresql_analyzer.py) — lack dedicated Robot Framework integration tests that exercise real component interactions end-to-end.

This issue tracks the work of identifying and filling those gaps with Robot Framework tests in the robot/ directory, in line with the project's integration testing standards (no mocks in Robot tests).

Subtasks

Audit existing Robot tests under robot/acms_*.robot and robot/m5_acms_smoke.robot to identify which sub-components and behaviours are already covered
Identify all public-facing behaviours of the acms module that lack integration-level Robot coverage (e.g., UKO vocabulary resolution, scope chain resolution, ontology registry lookups, temporal context, CRP, language analyzers)
Write Robot Framework test cases for the identified gaps using real component interactions (no mocks)
Ensure tests use appropriate Robot Framework tags (tdd_issue where applicable)
Verify all new tests pass via nox -e integration_tests
Confirm nox -e coverage_report still reports >= 97%

Definition of Done

Robot Framework integration tests exist covering the identified acms sub-component gaps
Tests exercise real component interactions without mocking (mocks only in features/mocks/ if needed for unit tests)
All new tests pass via nox -e integration_tests
All nox stages pass (nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e integration_tests, nox -e coverage_report)
Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on the current active milestone. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: new-issue-creator

## Metadata - **Branch**: `test-infra/robot-tests-acms` - **Commit Message**: `test(acms): add Robot Framework integration tests for the acms module` - **Milestone**: *(to be assigned — see backlog note below)* - **Parent Epic**: #5407 ## Overview The `acms` module (Advanced Context Management System) has several Robot Framework test files covering the pipeline, backends, and fusion layers (`acms_pipeline.robot`, `acms_backends.robot`, `acms_fusion.robot`, etc.), but integration-level coverage is incomplete. Key sub-components — including the UKO vocabulary layer (`src/cleveragents/acms/uko/`), scope resolution (`scope_resolution.py`), ontology registry (`ontology_registry.py`), temporal models (`temporal.py`), CRP (`crp.py`), and the various language analyzers (`python_analyzer.py`, `markdown_analyzer.py`, `docker_compose_analyzer.py`, `postgresql_analyzer.py`) — lack dedicated Robot Framework integration tests that exercise real component interactions end-to-end. This issue tracks the work of identifying and filling those gaps with Robot Framework tests in the `robot/` directory, in line with the project's integration testing standards (no mocks in Robot tests). ## Subtasks - [ ] Audit existing Robot tests under `robot/acms_*.robot` and `robot/m5_acms_smoke.robot` to identify which sub-components and behaviours are already covered - [ ] Identify all public-facing behaviours of the `acms` module that lack integration-level Robot coverage (e.g., UKO vocabulary resolution, scope chain resolution, ontology registry lookups, temporal context, CRP, language analyzers) - [ ] Write Robot Framework test cases for the identified gaps using real component interactions (no mocks) - [ ] Ensure tests use appropriate Robot Framework tags (`tdd_issue` where applicable) - [ ] Verify all new tests pass via `nox -e integration_tests` - [ ] Confirm `nox -e coverage_report` still reports >= 97% ## Definition of Done - [ ] Robot Framework integration tests exist covering the identified `acms` sub-component gaps - [ ] Tests exercise real component interactions without mocking (mocks only in `features/mocks/` if needed for unit tests) - [ ] All new tests pass via `nox -e integration_tests` - [ ] All nox stages pass (`nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`, `nox -e coverage_report`) - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on the current active milestone. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator

HAL9000 added a new dependency

2026-04-09 09:16:24 +00:00

#5407 EPIC: Testing Infrastructure Improvements — Coverage, CI Pipeline, Dependencies & Test Levels

HAL9000 added the

labels

2026-04-09 09:18:55 +00:00

HAL9000 added this to the v3.4.0 milestone

2026-04-09 09:20:33 +00:00

HAL9000 commented

2026-04-09 09:22:05 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 referenced this issue

2026-04-09 09:22:36 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 14) #5776

HAL9000 added

and removed

labels

2026-04-09 09:30:20 +00:00

HAL9000 referenced this issue

2026-04-09 09:56:03 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 29) #5788

HAL9000 commented

2026-04-09 10:12:57 +00:00

Author

Owner

🔄 State Transition: `State/Unverified` → `State/Verified`

Transition performed by: Forgejo Label Manager (automated)
Timestamp: 2026-04-09

Precondition Checks (All Passed ✅)

Check	Result	Detail
Valid starting state	✅	Was `State/Unverified`
Issue not locked	✅	`is_locked: false`
No blockers	✅	`blocked_by: null`
Clear descriptive title	✅	`TEST-INFRA: [missing-test-levels] Missing Robot tests for acms module`
`## Metadata` section present	✅	Branch + commit message defined
`## Subtasks` checklist present	✅	6 subtasks defined
`## Definition of Done` present	✅	5 DoD items defined
Parent Epic linked	✅	`#5407` referenced in body
Milestone assigned	✅	`v3.4.0`
Not a duplicate	✅	No `Duplicate` label
Type label present	✅	`Type/Testing`

Label Changes

Operation	Label	ID
➖ Removed	`State/Unverified`	`846`
➕ Added	`State/Verified`	`847`

Current Label Set (Post-Transition)

State/Verified ✅
Type/Testing
Priority/Backlog
MoSCoW/Should have

PRs Updated

No open PRs are linked to this issue — no PR label synchronization required.

Next Steps

This issue is now in the backlog (State/Verified). It is ready to be picked up and transitioned to State/In Progress when a contributor begins active work. Per CONTRIBUTING.md, the next transition requires:

A contributor assigned to the issue
A branch created matching the ## Metadata branch name: test-infra/robot-tests-acms

Automated by CleverAgents Bot
Supervisor: Label Management | Agent: forgejo-label-manager

## 🔄 State Transition: `State/Unverified` → `State/Verified` **Transition performed by:** Forgejo Label Manager (automated) **Timestamp:** 2026-04-09 ### Precondition Checks (All Passed ✅) | Check | Result | Detail | |-------|--------|--------| | Valid starting state | ✅ | Was `State/Unverified` | | Issue not locked | ✅ | `is_locked: false` | | No blockers | ✅ | `blocked_by: null` | | Clear descriptive title | ✅ | `TEST-INFRA: [missing-test-levels] Missing Robot tests for acms module` | | `## Metadata` section present | ✅ | Branch + commit message defined | | `## Subtasks` checklist present | ✅ | 6 subtasks defined | | `## Definition of Done` present | ✅ | 5 DoD items defined | | Parent Epic linked | ✅ | `#5407` referenced in body | | Milestone assigned | ✅ | `v3.4.0` | | Not a duplicate | ✅ | No `Duplicate` label | | Type label present | ✅ | `Type/Testing` | ### Label Changes | Operation | Label | ID | |-----------|-------|----| | ➖ **Removed** | `State/Unverified` | `846` | | ➕ **Added** | `State/Verified` | `847` | ### Current Label Set (Post-Transition) - `State/Verified` ✅ - `Type/Testing` - `Priority/Backlog` - `MoSCoW/Should have` ### PRs Updated No open PRs are linked to this issue — no PR label synchronization required. ### Next Steps This issue is now in the **backlog** (`State/Verified`). It is ready to be picked up and transitioned to `State/In Progress` when a contributor begins active work. Per CONTRIBUTING.md, the next transition requires: - A contributor assigned to the issue - A branch created matching the `## Metadata` branch name: `test-infra/robot-tests-acms` --- **Automated by CleverAgents Bot** Supervisor: Label Management | Agent: forgejo-label-manager

HAL9000 referenced this issue

2026-04-09 10:56:46 +00:00

[AUTO-EPIC] Epic Planning Health Report (Cycle 13) #5737