cleveragents/cleveragents-core

Fork 3

test(integration): verify M5 success criteria — ACMS and large-project context #406

New issue

Closed

opened 2026-02-23 22:17:30 +00:00 by freemo · 1 comment

freemo commented

2026-02-23 22:17:30 +00:00

Owner

Metadata

Commit Message: test(integration): verify M5 success criteria — ACMS and large-project context
Branch: test/m5-e2e-verification

Description

Robot Framework integration test suite that exercises the complete M5 success criteria verification sequence: indexing a large project (10,000+ files), verifying context tier management, and validating ACMS v1 pipeline output. Uses integration-appropriate mocking (e.g., mocked LLM providers).

Acceptance Criteria

Robot test creates a project with a 10,000+ file repository
Robot test registers and links a large git-checkout resource
Robot test verifies indexing completes without timeout
Assertions verify context window management works (hot/warm/cold tiers)
Assertions verify ACMS v1 pipeline produces scoped context output
nox passes with coverage >=97%

Verification Commands

# Full M5 verification sequence (from specification)
agents project create local/large-project
agents resource add git-checkout local/large-repo --path /path/to/large/repo --branch main
agents project link-resource local/large-project local/large-repo
agents project show local/large-project

Subtasks

Write Robot Framework integration test suite covering all acceptance criteria above
Verify all assertions pass against working implementation
Tests (Behave): N/A (this is an integration test issue)
Tests (Robot): The Robot test suite IS this issue's deliverable
Tests (ASV): N/A (no benchmark needed for integration verification)
Verify coverage >=97% via nox -s coverage_report
Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.

## Metadata - **Commit Message**: `test(integration): verify M5 success criteria — ACMS and large-project context` - **Branch**: `test/m5-e2e-verification` ## Description Robot Framework integration test suite that exercises the complete M5 success criteria verification sequence: indexing a large project (10,000+ files), verifying context tier management, and validating ACMS v1 pipeline output. Uses integration-appropriate mocking (e.g., mocked LLM providers). ## Acceptance Criteria - [ ] Robot test creates a project with a 10,000+ file repository - [ ] Robot test registers and links a large git-checkout resource - [ ] Robot test verifies indexing completes without timeout - [ ] Assertions verify context window management works (hot/warm/cold tiers) - [ ] Assertions verify ACMS v1 pipeline produces scoped context output - [ ] `nox` passes with coverage >=97% ## Verification Commands ```bash # Full M5 verification sequence (from specification) agents project create local/large-project agents resource add git-checkout local/large-repo --path /path/to/large/repo --branch main agents project link-resource local/large-project local/large-repo agents project show local/large-project ``` ## Subtasks - [ ] Write Robot Framework integration test suite covering all acceptance criteria above - [ ] Verify all assertions pass against working implementation - [ ] Tests (Behave): N/A (this is an integration test issue) - [ ] Tests (Robot): The Robot test suite IS this issue's deliverable - [ ] Tests (ASV): N/A (no benchmark needed for integration verification) - [ ] Verify coverage >=97% via `nox -s coverage_report` - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.

freemo added the

labels

2026-02-23 22:17:42 +00:00

freemo added this to the v3.4.0 milestone

2026-02-23 22:17:50 +00:00

freemo added the

labels

2026-02-24 03:35:58 +00:00

brent.edwards was assigned by freemo

2026-02-24 03:37:56 +00:00

freemo referenced this issue

2026-02-24 03:42:30 +00:00

Epic: ACMS Context Pipeline #396

~~freemo referenced this issue 2026-02-24 03:42:31 +00:00~~

Epic: Milestone Acceptance and Workflow Example Integration Tests #401

freemo added

and removed

labels

2026-02-24 21:54:30 +00:00

freemo commented

2026-02-24 21:54:49 +00:00

Author

Owner

Parent Epic: #401 (End-to-End Milestone Verification)

brent.edwards referenced this issue from a commit

2026-02-26 16:32:11 +00:00

test(e2e): verify M5 success criteria — ACMS and large-project context

brent.edwards referenced this issue from a pull request that will close it,

2026-02-26 16:32:25 +00:00

test(e2e): verify M5 success criteria — ACMS and large-project context #456

brent.edwards added

and removed

labels

2026-02-26 16:32:33 +00:00

brent.edwards

2026-02-27 20:37:12 +00:00

closed this issue
added
State
In Review
and removed
State
In Progress
labels

freemo referenced this issue

2026-03-02 01:56:42 +00:00

test(e2e): validate M5 acceptance criteria for v3.4.0 milestone closure #496

freemo added a new dependency

2026-03-02 02:13:37 +00:00

#496 test(e2e): validate M5 acceptance criteria for v3.4.0 milestone closure

freemo changed title from ~~test(e2e): verify M5 success criteria — ACMS and large-project context~~ to test(integration): verify M5 success criteria — ACMS and large-project context

2026-03-12 19:22:42 +00:00