UAT: 4 container tool routing scenarios in container_tool_exec.feature are permanently @skipped — ToolRunner container delegation untested #6115

Open
opened 2026-04-09 15:00:03 +00:00 by HAL9000 · 1 comment
Owner

Bug Report

Feature Area: Container Tool Execution — Test Coverage
Severity: Critical — core container routing behavior has no passing tests
Found by: UAT Testing (container-tool-execution worker)


What Was Tested

Code-level analysis of features/container_tool_exec.feature against the container tool execution specification.

Expected Behavior

The container_tool_exec.feature file should have passing tests for:

  1. ToolRunner delegating to ContainerToolExecutor when env is CONTAINER
  2. ToolRunner returning error when container executor is not configured
  3. ToolRunner returning error when ContainerUnavailableError is raised
  4. ToolRunner catching container executor exceptions

Actual Behavior

Four scenarios are permanently @skipped with @tdd_issue_4243:

@skip
Scenario: ToolRunner delegates to ContainerToolExecutor when env is CONTAINER
  ...

@skip
Scenario: ToolRunner returns error when container executor is not configured
  ...

@skip
Scenario: ToolRunner returns error when container env resolver raises ContainerUnavailableError
  ...

@skip
Scenario: ToolRunner catches container executor exception
  ...

These are the core behavioral tests for container routing. Without them, the container execution path has no automated test coverage. The @tdd_issue_4243 tag suggests these were skipped due to a known issue, but they remain skipped indefinitely.

Code Location

  • features/container_tool_exec.feature lines 126-127, 134-135, 455-456, 462-463, 474-475

Impact

The most critical container execution behaviors — delegation to ContainerToolExecutor, error handling when executor is absent, and exception catching — have no test coverage. Regressions in these paths will not be caught by CI.


Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area:** Container Tool Execution — Test Coverage **Severity:** Critical — core container routing behavior has no passing tests **Found by:** UAT Testing (container-tool-execution worker) --- ## What Was Tested Code-level analysis of `features/container_tool_exec.feature` against the container tool execution specification. ## Expected Behavior The `container_tool_exec.feature` file should have passing tests for: 1. `ToolRunner` delegating to `ContainerToolExecutor` when env is `CONTAINER` 2. `ToolRunner` returning error when container executor is not configured 3. `ToolRunner` returning error when `ContainerUnavailableError` is raised 4. `ToolRunner` catching container executor exceptions ## Actual Behavior Four scenarios are permanently `@skip`ped with `@tdd_issue_4243`: ```gherkin @skip Scenario: ToolRunner delegates to ContainerToolExecutor when env is CONTAINER ... @skip Scenario: ToolRunner returns error when container executor is not configured ... @skip Scenario: ToolRunner returns error when container env resolver raises ContainerUnavailableError ... @skip Scenario: ToolRunner catches container executor exception ... ``` These are the **core behavioral tests** for container routing. Without them, the container execution path has no automated test coverage. The `@tdd_issue_4243` tag suggests these were skipped due to a known issue, but they remain skipped indefinitely. ## Code Location - `features/container_tool_exec.feature` lines 126-127, 134-135, 455-456, 462-463, 474-475 ## Impact The most critical container execution behaviors — delegation to `ContainerToolExecutor`, error handling when executor is absent, and exception catching — have no test coverage. Regressions in these paths will not be caught by CI. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
HAL9000 added this to the v3.5.0 milestone 2026-04-09 15:32:04 +00:00
Author
Owner

Label compliance fix applied:

  • Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
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#6115
No description provided.