test(e2e): add M6 autonomy acceptance suite #211

New issue

Closed

opened 2026-02-22 23:40:08 +00:00 by freemo · 1 comment

freemo commented

2026-02-22 23:40:08 +00:00

Owner

Metadata

Commit Message: test(e2e): add M6 autonomy acceptance suite
Branch: feature/m6-autonomy-smoke

Background

E2E fixtures cover ACP facade flows and autonomy guardrails. The suite exercises guardrail enforcement (max steps, tool budget, confirmations) and audit trail persistence in integrated scenarios.

Acceptance Criteria

Add fixtures for ACP facade flows and autonomy guardrails.
Update docs/development/testing.md with M6 acceptance suite usage.

Definition of Done

This issue is complete when:

All subtasks below 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 body should be appropriate in size for a commit message and relatively
complete in describing what was done.
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.

Subtasks

Add fixtures for ACP facade flows and autonomy guardrails.
Update docs/development/testing.md with M6 acceptance suite usage.
Tests (Behave): Add features/m6_autonomy_acceptance.feature covering ACP facade, guardrails, and full local mode flow.
Tests (Robot): Add Robot integration suite for M6 acceptance run.
Tests (ASV): Add benchmarks/m6_acceptance_bench.py for runtime.
Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: #### M6: Autonomy Hardening + Server Stubs (Day 30)
Status: Open

## Metadata - **Commit Message**: `test(e2e): add M6 autonomy acceptance suite` - **Branch**: `feature/m6-autonomy-smoke` ## Background E2E fixtures cover ACP facade flows and autonomy guardrails. The suite exercises guardrail enforcement (max steps, tool budget, confirmations) and audit trail persistence in integrated scenarios. ## Acceptance Criteria - [ ] Add fixtures for ACP facade flows and autonomy guardrails. - [ ] Update `docs/development/testing.md` with M6 acceptance suite usage. ## Definition of Done This issue is complete when: - All subtasks below 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 body should be appropriate in size for a commit message and relatively complete in describing what was done. - 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. ## Subtasks - [ ] Add fixtures for ACP facade flows and autonomy guardrails. - [ ] Update `docs/development/testing.md` with M6 acceptance suite usage. - [ ] Tests (Behave): Add `features/m6_autonomy_acceptance.feature` covering ACP facade, guardrails, and full local mode flow. - [ ] Tests (Robot): Add Robot integration suite for M6 acceptance run. - [ ] Tests (ASV): Add `benchmarks/m6_acceptance_bench.py` for runtime. - [ ] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: #### M6: Autonomy Hardening + Server Stubs (Day 30) **Status**: Open

Rows
Columns