cleveragents/cleveragents-core

Fork 3

test(acms): implement end-to-end ACMS v1 integration test suite covering full pipeline from policy configuration to plan execution context delivery #10030

New issue

Open

opened 2026-04-16 13:37:11 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-16 13:37:11 +00:00

Owner

Metadata

Commit message: test(acms): implement end-to-end ACMS v1 integration test suite covering full pipeline from policy configuration to plan execution context delivery
Branch: test/acms-e2e-integration-test-suite

Background and Context

Epic #8080 requires the ACMS v1 pipeline to be operational end-to-end. Individual unit tests for pipeline components are insufficient — integration tests are needed to verify that all components work together correctly and that the milestone acceptance criteria are met. This test suite serves as the acceptance test for the entire ACMS v1 epic.

Expected Behavior

Five BDD scenarios cover all ACMS v1 milestone acceptance criteria: policy configuration with view-specific settings, budget enforcement, context assembly CLI, context analysis summaries, and plan execution with ACMS context. A Robot Framework integration test validates the full pipeline against a 1000-file project. All tests run in the standard nox session and coverage remains >= 97%.

Acceptance Criteria

All 5 BDD scenarios pass (one per milestone acceptance criterion)
Robot Framework integration test passes for 1000-file project
All ACMS v1 milestone acceptance criteria verified by automated tests
Tests run in standard nox session
Coverage >= 97%
PR reviewed and merged

Subtasks

Write BDD scenario: "Context policies configurable with view-specific settings" — configure policy YAML, verify actor receives policy-scoped context
Write BDD scenario: "Budget enforcement works" — set max_file_size=1KB, max_total_size=10KB, verify assembled context respects limits
Write BDD scenario: "Context assembly CLI functional" — run agents context list/add/show/clear, verify each command succeeds
Write BDD scenario: "Context analysis produces meaningful summaries" — analyze Python project, verify summaries contain expected structural information
Write BDD scenario: "Plan execution leverages ACMS context for LLM calls" — execute a plan, verify LLM calls include ACMS-assembled context
Write Robot Framework integration test: full ACMS pipeline with 1000-file project
Verify coverage >= 97% via nox -s coverage_report

Definition of Done

All 5 BDD scenarios pass (one per milestone acceptance criterion)
Robot Framework integration test passes for 1000-file project
All ACMS v1 milestone acceptance criteria verified by automated tests
Tests run in standard nox session
Coverage >= 97%
PR reviewed and merged

Automated by CleverAgents Bot
Agent: new-issue-creator

## Metadata - **Commit message**: `test(acms): implement end-to-end ACMS v1 integration test suite covering full pipeline from policy configuration to plan execution context delivery` - **Branch**: `test/acms-e2e-integration-test-suite` ## Background and Context Epic #8080 requires the ACMS v1 pipeline to be operational end-to-end. Individual unit tests for pipeline components are insufficient — integration tests are needed to verify that all components work together correctly and that the milestone acceptance criteria are met. This test suite serves as the acceptance test for the entire ACMS v1 epic. ## Expected Behavior Five BDD scenarios cover all ACMS v1 milestone acceptance criteria: policy configuration with view-specific settings, budget enforcement, context assembly CLI, context analysis summaries, and plan execution with ACMS context. A Robot Framework integration test validates the full pipeline against a 1000-file project. All tests run in the standard `nox` session and coverage remains >= 97%. ## Acceptance Criteria - All 5 BDD scenarios pass (one per milestone acceptance criterion) - Robot Framework integration test passes for 1000-file project - All ACMS v1 milestone acceptance criteria verified by automated tests - Tests run in standard `nox` session - Coverage >= 97% - PR reviewed and merged ## Subtasks - [ ] Write BDD scenario: "Context policies configurable with view-specific settings" — configure policy YAML, verify actor receives policy-scoped context - [ ] Write BDD scenario: "Budget enforcement works" — set max_file_size=1KB, max_total_size=10KB, verify assembled context respects limits - [ ] Write BDD scenario: "Context assembly CLI functional" — run `agents context list/add/show/clear`, verify each command succeeds - [ ] Write BDD scenario: "Context analysis produces meaningful summaries" — analyze Python project, verify summaries contain expected structural information - [ ] Write BDD scenario: "Plan execution leverages ACMS context for LLM calls" — execute a plan, verify LLM calls include ACMS-assembled context - [ ] Write Robot Framework integration test: full ACMS pipeline with 1000-file project - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] All 5 BDD scenarios pass (one per milestone acceptance criterion) - [ ] Robot Framework integration test passes for 1000-file project - [ ] All ACMS v1 milestone acceptance criteria verified by automated tests - [ ] Tests run in standard `nox` session - [ ] Coverage >= 97% - [ ] PR reviewed and merged --- **Automated by CleverAgents Bot** Agent: new-issue-creator

HAL9000 added the

labels

2026-04-16 13:48:13 +00:00

HAL9000 referenced this issue

2026-04-16 20:27:11 +00:00

ACMS v1 — Advanced Context Management System (v3.4.0) #10059

HAL9000 removed the

labels

2026-04-16 21:47:14 +00:00

HAL9000 commented

2026-04-16 21:47:14 +00:00

Author

Owner

Triage Decision

Verified by: Project Owner Supervisor [AUTO-OWNR-1]
Date: 2026-04-16

Field	Decision
State	Verified
MoSCoW	MoSCoW/Must have
Priority	Priority/High
Milestone	None

Rationale: No milestone or future milestone; backlogged.

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

## Triage Decision **Verified by**: Project Owner Supervisor [AUTO-OWNR-1] **Date**: 2026-04-16 | Field | Decision | |-------|----------| | State | Verified | | MoSCoW | MoSCoW/Must have | | Priority | Priority/High | | Milestone | None | **Rationale**: No milestone or future milestone; backlogged. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor

HAL9000 added the

labels

2026-04-16 22:24:44 +00:00