test(integration): verify M3 success criteria — decision tree and correction #404

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

Metadata

  • Commit Message: test(integration): verify M3 success criteria — decision tree and correction
  • Branch: test/m3-e2e-verification

Description

Robot Framework integration test suite that exercises the complete M3 success criteria verification sequence: plan execution with decision generation, decision tree viewing, decision explanation, invariant management, and decision correction (dry-run and live). Uses integration-appropriate mocking (e.g., mocked LLM providers).

Acceptance Criteria

  • Robot test executes a plan that generates decisions during Strategize
  • Robot test views the decision tree via agents plan tree
  • Robot test explains a specific decision via agents plan explain
  • Robot test adds and lists project invariants
  • Robot test performs a dry-run correction via agents plan correct --dry-run
  • Robot test executes a live correction in revert mode
  • Assertions verify decisions are recorded with full context snapshot
  • Assertions verify decision tree persists to database and renders correctly
  • Assertions verify correction in revert mode re-executes from decision point
  • Assertions verify invariants are enforced during strategize
  • nox passes with coverage >=97%

Verification Commands

# Full M3 verification sequence (from specification)
agents plan use local/complex-action local/large-project
agents plan execute <plan_id>
agents plan tree <plan_id>
agents plan explain <decision_id>
agents invariant add --project local/large-project "Use session cookies"
agents invariant list --project local/large-project
agents plan correct <decision_id> --mode=revert --guidance "Use session cookies instead of JWT" --dry-run
agents plan correct <decision_id> --mode=revert --guidance "Use session cookies instead of JWT"

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 M3 success criteria — decision tree and correction` - **Branch**: `test/m3-e2e-verification` ## Description Robot Framework integration test suite that exercises the complete M3 success criteria verification sequence: plan execution with decision generation, decision tree viewing, decision explanation, invariant management, and decision correction (dry-run and live). Uses integration-appropriate mocking (e.g., mocked LLM providers). ## Acceptance Criteria - [ ] Robot test executes a plan that generates decisions during Strategize - [ ] Robot test views the decision tree via `agents plan tree` - [ ] Robot test explains a specific decision via `agents plan explain` - [ ] Robot test adds and lists project invariants - [ ] Robot test performs a dry-run correction via `agents plan correct --dry-run` - [ ] Robot test executes a live correction in revert mode - [ ] Assertions verify decisions are recorded with full context snapshot - [ ] Assertions verify decision tree persists to database and renders correctly - [ ] Assertions verify correction in revert mode re-executes from decision point - [ ] Assertions verify invariants are enforced during strategize - [ ] `nox` passes with coverage >=97% ## Verification Commands ```bash # Full M3 verification sequence (from specification) agents plan use local/complex-action local/large-project agents plan execute <plan_id> agents plan tree <plan_id> agents plan explain <decision_id> agents invariant add --project local/large-project "Use session cookies" agents invariant list --project local/large-project agents plan correct <decision_id> --mode=revert --guidance "Use session cookies instead of JWT" --dry-run agents plan correct <decision_id> --mode=revert --guidance "Use session cookies instead of JWT" ``` ## 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 this to the v3.2.0 milestone 2026-02-23 22:17:49 +00:00
Author
Owner

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

Parent Epic: #401 (End-to-End Milestone Verification)
freemo changed title from test(e2e): verify M3 success criteria — decision tree and correction to test(integration): verify M3 success criteria — decision tree and correction 2026-03-12 19:22:33 +00:00
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#404
No description provided.