TDD: TUI commands bypass A2A facade and call get_container() directly #10441

New issue

Open

opened 2026-04-18 09:38:54 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-18 09:38:54 +00:00

Owner

Metadata

Commit Message: test(tui): add tdd test capturing direct get_container() calls bypassing A2A facade
Branch: tdd/m8-tui-commands-a2a-facade-routing

Background and Context

This is the TDD issue-capture test for bug #10369: UAT: TUI commands bypass A2A facade and call get_container() directly.

Per the Bug Fix Workflow, a failing test must be written before the fix is implemented. This test captures the buggy behavior (direct get_container() calls in TUI commands instead of routing through the A2A facade).

Test to Write

Add a Behave BDD scenario tagged with @tdd_issue @tdd_issue_10369 @tdd_expected_fail that:

Inspects TuiCommandRouter for A2A facade usage
Verifies that TuiCommandRouter does NOT call get_container() directly
Verifies that run_tui() does NOT call get_container() directly
Asserts that A2A facade routing is used (this assertion will fail while the bug is unfixed)

The test must use AssertionError (not other exceptions) to signal the bug is still present.

Acceptance Criteria

A Behave BDD scenario exists tagged @tdd_issue @tdd_issue_10369 @tdd_expected_fail
The scenario verifies A2A facade routing in TuiCommandRouter
The test passes CI (inverted by @tdd_expected_fail tag) while the bug is unfixed

Subtasks

Add TDD scenario to an appropriate feature file (e.g., features/tui_commands_coverage.feature)
Create step definitions for the TDD scenario
Tag scenario with @tdd_issue @tdd_issue_10369 @tdd_expected_fail
Verify test passes CI with @tdd_expected_fail tag
Run nox -s unit_tests to confirm

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.

Automated by CleverAgents Bot
Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

## Metadata - **Commit Message**: `test(tui): add tdd test capturing direct get_container() calls bypassing A2A facade` - **Branch**: `tdd/m8-tui-commands-a2a-facade-routing` ## Background and Context This is the TDD issue-capture test for bug #10369: `UAT: TUI commands bypass A2A facade and call get_container() directly`. Per the Bug Fix Workflow, a failing test must be written before the fix is implemented. This test captures the buggy behavior (direct `get_container()` calls in TUI commands instead of routing through the A2A facade). ## Test to Write Add a Behave BDD scenario tagged with `@tdd_issue @tdd_issue_10369 @tdd_expected_fail` that: 1. Inspects `TuiCommandRouter` for A2A facade usage 2. Verifies that `TuiCommandRouter` does NOT call `get_container()` directly 3. Verifies that `run_tui()` does NOT call `get_container()` directly 4. Asserts that A2A facade routing is used (this assertion will fail while the bug is unfixed) The test must use `AssertionError` (not other exceptions) to signal the bug is still present. ## Acceptance Criteria - [ ] A Behave BDD scenario exists tagged `@tdd_issue @tdd_issue_10369 @tdd_expected_fail` - [ ] The scenario verifies A2A facade routing in `TuiCommandRouter` - [ ] The test passes CI (inverted by `@tdd_expected_fail` tag) while the bug is unfixed ## Subtasks - [ ] Add TDD scenario to an appropriate feature file (e.g., `features/tui_commands_coverage.feature`) - [ ] Create step definitions for the TDD scenario - [ ] Tag scenario with `@tdd_issue @tdd_issue_10369 @tdd_expected_fail` - [ ] Verify test passes CI with `@tdd_expected_fail` tag - [ ] Run `nox -s unit_tests` to confirm ## 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. --- **Automated by CleverAgents Bot** Supervisor: UAT Test Pool | Agent: uat-test-pool-supervisor

HAL9000 added the

labels

2026-04-18 09:41:00 +00:00