test(e2e): add M5 ACMS + context suites #469

Merged

brent.edwards merged 10 commits from feature/m5-acms-smoke into master 2026-02-28 05:24:10 +00:00

Conversation 0 Commits 10 Files changed 10 +1234 -1

brent.edwards commented 2026-02-27 20:20:46 +00:00

Member

Copy link

Summary

Closes #200

Adds comprehensive M5 ACMS and context management smoke test suites covering:

Behave BDD Scenarios (27 scenarios)

• Context policy phase inheritance (default → strategize → execute → apply)
• Context view field validation and max-size constraints
• ContextService CRUD operations (add/remove/list/show)
• Context analysis agent pipeline stages
• CLI context commands (add/remove/list/show/clear/export/import)
• Project context policy CLI (inspect/simulate stubs raise NotImplementedError)
• Large project context scalability (500-file simulation)
• Context search and relevance scoring

Robot Integration Tests (10 tests)

• Context policy round-trip serialisation
• Phase inheritance chain validation
• Context file metadata integrity
• Analysis pipeline stage completeness
• CLI context subcommand availability
• Large project context scalability

ASV Performance Benchmarks (4 suites)

• ContextPolicy creation and phase lookup
• ContextService add/remove/list operations
• Context analysis pipeline overhead
• Large project context handling

Fixtures

• features/fixtures/m5/acms_context_policy.json — Phase-specific context policy
• features/fixtures/m5/large_project_context.json — 500-file project simulation
• features/fixtures/m5/context_analysis_results.json — Pre-computed analysis results

Documentation

• Updated docs/development/testing.md with M5 suite documentation

## Summary Closes #200 Adds comprehensive M5 ACMS and context management smoke test suites covering: ### Behave BDD Scenarios (27 scenarios) - Context policy phase inheritance (default → strategize → execute → apply) - Context view field validation and max-size constraints - ContextService CRUD operations (add/remove/list/show) - Context analysis agent pipeline stages - CLI context commands (add/remove/list/show/clear/export/import) - Project context policy CLI (inspect/simulate stubs raise NotImplementedError) - Large project context scalability (500-file simulation) - Context search and relevance scoring ### Robot Integration Tests (10 tests) - Context policy round-trip serialisation - Phase inheritance chain validation - Context file metadata integrity - Analysis pipeline stage completeness - CLI context subcommand availability - Large project context scalability ### ASV Performance Benchmarks (4 suites) - ContextPolicy creation and phase lookup - ContextService add/remove/list operations - Context analysis pipeline overhead - Large project context handling ### Fixtures - `features/fixtures/m5/acms_context_policy.json` — Phase-specific context policy - `features/fixtures/m5/large_project_context.json` — 500-file project simulation - `features/fixtures/m5/context_analysis_results.json` — Pre-computed analysis results ### Documentation - Updated `docs/development/testing.md` with M5 suite documentation

brent.edwards self-assigned this 2026-02-27 20:20:47 +00:00

brent.edwards added 1 commit 2026-02-27 20:20:47 +00:00

test(e2e): add M5 ACMS + context suites ece5e61725

brent.edwards added 1 commit 2026-02-27 22:25:31 +00:00

fix(test): correct M5 smoke patch targets and pattern matching ... 75c628793b

Fix 4 errored scenarios: patch get_container instead of the lazily-
imported ContextService (which is not a module-level attribute of
cleveragents.cli.commands.context).

Fix project context show (line 112): mock _get_namespaced_project_repo
to return a repo (not a tuple), mock get_container for session_factory,
and mock _read_policy to bypass DB access.

Fix context exclusion pattern (line 152): replace fnmatch.fnmatch with
PurePosixPath.match for proper ** glob handling and use a path with a
leading directory segment.

Also fix context list empty assertion to match actual CLI output
('No files in context' rather than 'No context'), and patch
Path.exists for the add command so the mock service is reached.

brent.edwards added 1 commit 2026-02-27 22:45:54 +00:00

Merge branch 'master' into feature/m5-acms-smoke c9782637d9

brent.edwards added 1 commit 2026-02-27 23:42:34 +00:00

refactor(cli): promote get_container to module-level import ... 58d593322c

Move get_container from lazy per-function imports to module-level in
context.py (10 sites) and project_context.py (3 sites).  This makes
the symbol a patchable module attribute so BDD step files can
mock the DI container with unittest.mock.patch.

Closes #200

brent.edwards added 1 commit 2026-02-27 23:43:18 +00:00

Merge branch 'master' into feature/m5-acms-smoke 50b047056e

brent.edwards added 1 commit 2026-02-28 00:59:12 +00:00

fix(test): use source-module patch target for get_container ... de8c33cb4a

Revert module-level import refactor and instead patch at
cleveragents.application.container.get_container — matching the
established pattern used by all existing context CLI tests.
Lazy imports inside each function re-read from the source module,
so patching there intercepts correctly.

Closes #200

freemo added the

Type

Testing

label 2026-02-28 02:14:52 +00:00

brent.edwards added 1 commit 2026-02-28 02:32:52 +00:00

Merge branch 'master' into feature/m5-acms-smoke e3a93bf32c

brent.edwards added 1 commit 2026-02-28 03:32:01 +00:00

fix(test): stabilize retry_with_timeout scenario ... 465683fb6b

Patch time.monotonic alongside time.sleep in the retry timeout step
so stop_after_delay cannot elapse due to wall-clock overhead on
busy CI runners. The fake monotonic clock advances by 1µs per call,
keeping elapsed time well under the 0.01s timeout while preserving
retry semantics.

Closes #200

brent.edwards added 1 commit 2026-02-28 03:32:34 +00:00

Merge branch 'master' into feature/m5-acms-smoke ab3431c671

brent.edwards added 1 commit 2026-02-28 04:29:09 +00:00

Merge branch 'master' into feature/m5-acms-smoke 133830c2b7

brent.edwards scheduled this pull request to auto merge when all checks succeed 2026-02-28 04:30:52 +00:00

brent.edwards merged commit ed2918c337 into master 2026-02-28 05:24:10 +00:00

brent.edwards deleted branch feature/m5-acms-smoke 2026-02-28 05:24:11 +00:00

brent.edwards referenced this pull request from a commit 2026-02-28 05:24:11 +00:00

Merge pull request 'test(e2e): add M5 ACMS + context suites' (#469) from feature/m5-acms-smoke into master

freemo added the

State

Completed

label 2026-03-04 00:41:55 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  

auto/blocked-by-deps

PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  

auto/ci-timeout

Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  

auto/claimed-implementer

Currently being processed by an implementer worker.

  

auto/claimed-merge

Currently being processed by the merge driver.

  

auto/claimed-reviewer

Currently being processed by a reviewer worker.

  

auto/driver-down

Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  

auto/invariant-violation

Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  

auto/last-attempt-tier-0

In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-1

In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  

auto/last-attempt-tier-2

In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  

auto/last-attempt-tier-min

In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  

Automation Tracking

Tracking issues used by the AI Automation system for agents to communicate and report.

  

auto/needs-conflict-resolution

Rebase conflict needs LLM conflict-resolver.

  

auto/needs-implementer

Failing CI needs implementer attention.

  

auto/postmortem

Documenting a driver incident or rollback.

  

auto/ready-to-merge

Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  

auto/restart-throttled

Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  

auto/revert

Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  

auto/sentinel

Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  

auto/stale-inactivity

No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  

auto/unstable

Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  

Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  

Bounty

$100

A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$1000

A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$10000

A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$20

A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$2000

A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$250

A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$50

A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$500

A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$5000

A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  

Bounty

$750

A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  

MoSCoW

Could have

Could have feature in order to satisfy the epic/legendary.

  

MoSCoW

Must have

Must have feature in order to satisfy the epic/legendary.

  

MoSCoW

Should have

Should have feature in order to satisfy the epic/legendary.

  

Needs Feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  

Points

1

1 man-hours worth of work for an expert with no learning curve.

  

Points

13

13 man-hours worth of work for an expert with no learning curve.

  

Points

2

2 man-hours worth of work for an expert with no learning curve.

  

Points

21

21 man-hours worth of work for an expert with no learning curve.

  

Points

3

3 man-hours worth of work for an expert with no learning curve.

  

Points

34

34 man-hours worth of work for an expert with no learning curve.

  

Points

5

5 man-hours worth of work for an expert with no learning curve.

  

Points

55

55 man-hours worth of work for an expert with no learning curve.

  

Points

8

8 man-hours worth of work for an expert with no learning curve.

  

Points

88

88 man-hours worth of work for an expert with no learning curve.

  

Priority

Backlog

This ticket has backlogged priority and is not to be worked on yet

  

Priority

CI Blocker

Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  

Priority

Critical

The priority is critical

  

Priority

High

The priority is high

  

Priority

Low

The priority is low

  

Priority

Medium

The priority is medium

  

Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  

Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  

State

Completed

The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  

State

Duplicate

A ticket that represents the same content as an existing ticket.

  

State

In Progress

A ticket that is actively being developed.

  

State

In Review

A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  

State

Paused

This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  

State

Unverified

All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  

State

Verified

The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  

State

Wont Do

This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  

Type

Automation

Any edits or discussion about the AI automated coding system.

  

Type

Bug

Something that doesnt work as intended.

  

Type

Discussion

Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  

Type

Documentation

An error or improvement needed in the documentation.

  

Type

Epic

Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  

Type

Feature

Some new functionality not present.

  

Type

Legendary

A type of Epic which will contain other Epics.

  

Type

Refactor

A code change that restructures existing code without changing its external behavior.

  

Type

Support

Someone needs help using the project.

  

Type

Task

A generic task that doesnt fit into the other type categories.

  

Type

Testing

Work exclusively focusing on fixing or expanding testing.

No labels

auto/needs-reevaluation

controller-managed

auto/blocked-by-deps

auto/ci-timeout

auto/claimed-implementer

auto/claimed-merge

auto/claimed-reviewer

auto/driver-down

auto/invariant-violation

auto/last-attempt-tier-0

auto/last-attempt-tier-1

auto/last-attempt-tier-2

auto/last-attempt-tier-min

Automation Tracking

auto/needs-conflict-resolution

auto/needs-implementer

auto/postmortem

auto/ready-to-merge

auto/restart-throttled

auto/revert

auto/sentinel

auto/stale-inactivity

auto/unstable

Blocked

Bounty

$100

Bounty

$1000

Bounty

$10000

Bounty

$20

Bounty

$2000

Bounty

$250

Bounty

$50

Bounty

$500

Bounty

$5000

Bounty

$750

MoSCoW

Could have

MoSCoW

Must have

MoSCoW

Should have

Needs Feedback

Points

1

Points

13

Points

2

Points

21

Points

3

Points

34

Points

5

Points

55

Points

8

Points

88

Priority

Backlog

Priority

CI Blocker

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Signed-off: Owner

Signed-off: Scrum Master

Signed-off: Tech Lead

Spike

State

Completed

State

Duplicate

State

In Progress

State

In Review

State

Paused

State

Unverified

State

Verified

State

Wont Do

Type

Automation

Type

Bug

Type

Discussion

Type

Documentation

Type

Epic

Type

Feature

Type

Legendary

Type

Refactor

Type

Support

Type

Task

Type

Testing

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

brent.edwards

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

cleveragents/cleveragents-core!469

No description provided.