test(integration): implement v3.2.0 milestone acceptance criteria integration test suite #8981

Open
opened 2026-04-14 04:35:01 +00:00 by HAL9000 · 1 comment
Owner

Background and Context

Epic #401 requires each milestone to have a dedicated integration test suite validating its full feature set using integration-appropriate mocking (e.g., mocked LLM providers). The v3.2.0 milestone (M3: Decisions + Validations + Invariants) delivers decision recording, the decision tree, agents plan explain, invariant management, and plan correction. Without a dedicated integration test suite for this milestone, there is no automated regression guard ensuring the M3 feature set continues to work correctly as the codebase evolves.

Expected Behavior

When this issue is complete:

  • A Robot Framework integration test suite (tests/integration/milestones/v3_2_0_acceptance.robot) exists
  • The suite validates all v3.2.0 acceptance criteria using mocked LLM providers (no real API keys required)
  • The suite runs within the standard nox -s integration_tests session
  • All test cases pass and are not tagged @E2E

Acceptance Criteria

  • Robot Framework suite tests/integration/milestones/v3_2_0_acceptance.robot exists and runs under nox -s integration_tests
  • Suite validates: decisions are recorded during Strategize with full context snapshots (mocked LLM)
  • Suite validates: agents plan tree renders the decision tree correctly
  • Suite validates: agents plan explain shows decision details including alternatives considered
  • Suite validates: agents invariant add creates invariants; agents invariant list displays them
  • Suite validates: invariants are enforced during strategize (mocked LLM)
  • Suite validates: agents plan correct --mode=revert re-executes from the targeted decision point
  • Suite validates: agents plan correct --mode=append adds guidance without recomputing
  • Output validation uses flexible matching (structural checks, not exact character matching)
  • Suite is NOT tagged @E2E and runs in the standard integration test session
  • Test coverage contribution brings overall coverage to >= 97%

Subtasks

  • Create tests/integration/milestones/ directory if it does not exist
  • Write v3_2_0_acceptance.robot with test cases for each v3.2.0 acceptance criterion
  • Configure mocked LLM provider fixture for integration tests
  • Write test case for decision recording during Strategize
  • Write test case for agents plan tree rendering
  • Write test case for agents plan explain output
  • Write test cases for agents invariant add and agents invariant list
  • Write test case for invariant enforcement during strategize
  • Write test cases for agents plan correct --mode=revert and --mode=append
  • Run suite under nox -s integration_tests and verify all tests pass
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

  • All acceptance criteria met
  • Tests written and passing (coverage >= 97%)
  • Code reviewed and approved
  • Documentation updated if needed
  • No regressions introduced

Metadata

  • Commit message: test(integration): implement v3.2.0 milestone acceptance criteria integration test suite
  • Branch name: test/integration-v3-2-0-milestone-acceptance

Automated by CleverAgents Bot
Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor

## Background and Context Epic #401 requires each milestone to have a dedicated integration test suite validating its full feature set using integration-appropriate mocking (e.g., mocked LLM providers). The v3.2.0 milestone (M3: Decisions + Validations + Invariants) delivers decision recording, the decision tree, `agents plan explain`, invariant management, and plan correction. Without a dedicated integration test suite for this milestone, there is no automated regression guard ensuring the M3 feature set continues to work correctly as the codebase evolves. ## Expected Behavior When this issue is complete: - A Robot Framework integration test suite (`tests/integration/milestones/v3_2_0_acceptance.robot`) exists - The suite validates all v3.2.0 acceptance criteria using mocked LLM providers (no real API keys required) - The suite runs within the standard `nox -s integration_tests` session - All test cases pass and are not tagged `@E2E` ## Acceptance Criteria - [ ] Robot Framework suite `tests/integration/milestones/v3_2_0_acceptance.robot` exists and runs under `nox -s integration_tests` - [ ] Suite validates: decisions are recorded during Strategize with full context snapshots (mocked LLM) - [ ] Suite validates: `agents plan tree` renders the decision tree correctly - [ ] Suite validates: `agents plan explain` shows decision details including alternatives considered - [ ] Suite validates: `agents invariant add` creates invariants; `agents invariant list` displays them - [ ] Suite validates: invariants are enforced during strategize (mocked LLM) - [ ] Suite validates: `agents plan correct --mode=revert` re-executes from the targeted decision point - [ ] Suite validates: `agents plan correct --mode=append` adds guidance without recomputing - [ ] Output validation uses flexible matching (structural checks, not exact character matching) - [ ] Suite is NOT tagged `@E2E` and runs in the standard integration test session - [ ] Test coverage contribution brings overall coverage to >= 97% ## Subtasks - [ ] Create `tests/integration/milestones/` directory if it does not exist - [ ] Write `v3_2_0_acceptance.robot` with test cases for each v3.2.0 acceptance criterion - [ ] Configure mocked LLM provider fixture for integration tests - [ ] Write test case for decision recording during Strategize - [ ] Write test case for `agents plan tree` rendering - [ ] Write test case for `agents plan explain` output - [ ] Write test cases for `agents invariant add` and `agents invariant list` - [ ] Write test case for invariant enforcement during strategize - [ ] Write test cases for `agents plan correct --mode=revert` and `--mode=append` - [ ] Run suite under `nox -s integration_tests` and verify all tests pass - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done - [ ] All acceptance criteria met - [ ] Tests written and passing (coverage >= 97%) - [ ] Code reviewed and approved - [ ] Documentation updated if needed - [ ] No regressions introduced ## Metadata - **Commit message:** `test(integration): implement v3.2.0 milestone acceptance criteria integration test suite` - **Branch name:** `test/integration-v3-2-0-milestone-acceptance` --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.2.0 milestone 2026-04-14 04:45:23 +00:00
Author
Owner

Verified — v3.2.0 acceptance criteria integration test suite is required for milestone completion. MoSCoW: Must-have. Priority: Medium.


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

✅ **Verified** — v3.2.0 acceptance criteria integration test suite is required for milestone completion. MoSCoW: Must-have. Priority: Medium. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#8981
No description provided.