cleveragents/cleveragents-core

Fork 3

UAT: wf17_explicit_container.robot has all test cases using Skip — no real assertions for container mounting workflow #6003

New issue

Open

opened 2026-04-09 13:32:04 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 13:32:04 +00:00

Owner

Bug Report

Feature Area: E2E Workflow Specification Tests — WF17 Explicit Container with Directory Mount
Milestone: v3.6.0 (M7) — E2E workflow specification tests
Severity: Priority/Backlog — test infrastructure gap, not blocking runtime

What Was Tested

Code-level analysis of robot/e2e/wf17_explicit_container.robot against Specification Example 17: Explicit Container with Directory Mount.

Expected Behavior (from spec)

Specification Example 17 describes a trusted-profile workflow:

Register git-checkout resource
Register container-instance resource with dual mounts (resource-ref rw + host-path ro)
Create project with linked container resource
Set execution environment override via project context set --execution-env-priority override
Create action with trusted automation profile
Run full plan lifecycle

The test file has 4 test cases covering different acceptance criteria.

Actual Behavior

All 4 test cases use Skip with "Test implementation pending" messages:

WF17 Explicit Container With Directory Mount Trusted Profile
  [Tags]    tdd_issue tdd_issue_4188
  [Timeout]    20 minutes
  # TDD placeholder - test implementation pending
  Skip    Test implementation pending for WF17 container mounting

WF17 TDD Dual Mount Registration
  [Tags]    tdd_issue tdd_issue_4188 tdd_issue_1078 tdd_issue_4178
  [Timeout]    5 minutes
  # TDD placeholder - test implementation pending
  Skip    Test implementation pending for dual mount registration

WF17 TDD Project Level Execution Env Priority Override
  [Tags]    tdd_issue tdd_issue_4188 tdd_issue_1079 tdd_issue_4178
  [Timeout]    5 minutes
  # TDD placeholder - test implementation pending
  Skip    Test implementation pending for project-level execution environment override

WF17 TDD Precedence Level 2 Project Override Resolution
  [Tags]    tdd_issue tdd_issue_4188 tdd_issue_1080 tdd_issue_4178
  [Timeout]    10 minutes
  # TDD placeholder - test implementation pending
  Skip    Test implementation pending for precedence level 2 project override resolution

All 4 tests skip unconditionally. No container mounting, no execution environment priority, no precedence resolution is tested.

Code Location

File: robot/e2e/wf17_explicit_container.robot
Lines 59-131: All 4 test cases — each contains only Skip

Impact

The WF17 E2E test provides zero coverage of the explicit container with directory mount workflow. The container-instance resource type, dual mount registration, execution environment priority override, and precedence resolution are all untested end-to-end.

Unlike tdd_expected_fail tests (which at least attempt to run and fail), these tests skip entirely, providing no signal about whether the underlying features work.

Definition of Done

The test cases should be implemented with real assertions:

WF17 Explicit Container With Directory Mount Trusted Profile: Full workflow from resource registration to plan apply
WF17 TDD Dual Mount Registration: Register container-instance with --mount resource-ref:rw and --mount host-path:ro, verify both mounts are stored
WF17 TDD Project Level Execution Env Priority Override: Set --execution-env-priority override via project context set, verify it persists
WF17 TDD Precedence Level 2 Project Override Resolution: Verify execution environment resolves via project-level override when no plan-level override is present

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

## Bug Report **Feature Area**: E2E Workflow Specification Tests — WF17 Explicit Container with Directory Mount **Milestone**: v3.6.0 (M7) — E2E workflow specification tests **Severity**: Priority/Backlog — test infrastructure gap, not blocking runtime ### What Was Tested Code-level analysis of `robot/e2e/wf17_explicit_container.robot` against Specification Example 17: Explicit Container with Directory Mount. ### Expected Behavior (from spec) Specification Example 17 describes a trusted-profile workflow: 1. Register git-checkout resource 2. Register container-instance resource with dual mounts (resource-ref rw + host-path ro) 3. Create project with linked container resource 4. Set execution environment override via `project context set --execution-env-priority override` 5. Create action with trusted automation profile 6. Run full plan lifecycle The test file has 4 test cases covering different acceptance criteria. ### Actual Behavior All 4 test cases use `Skip` with "Test implementation pending" messages: ```robot WF17 Explicit Container With Directory Mount Trusted Profile [Tags] tdd_issue tdd_issue_4188 [Timeout] 20 minutes # TDD placeholder - test implementation pending Skip Test implementation pending for WF17 container mounting WF17 TDD Dual Mount Registration [Tags] tdd_issue tdd_issue_4188 tdd_issue_1078 tdd_issue_4178 [Timeout] 5 minutes # TDD placeholder - test implementation pending Skip Test implementation pending for dual mount registration WF17 TDD Project Level Execution Env Priority Override [Tags] tdd_issue tdd_issue_4188 tdd_issue_1079 tdd_issue_4178 [Timeout] 5 minutes # TDD placeholder - test implementation pending Skip Test implementation pending for project-level execution environment override WF17 TDD Precedence Level 2 Project Override Resolution [Tags] tdd_issue tdd_issue_4188 tdd_issue_1080 tdd_issue_4178 [Timeout] 10 minutes # TDD placeholder - test implementation pending Skip Test implementation pending for precedence level 2 project override resolution ``` All 4 tests skip unconditionally. No container mounting, no execution environment priority, no precedence resolution is tested. ### Code Location - File: `robot/e2e/wf17_explicit_container.robot` - Lines 59-131: All 4 test cases — each contains only `Skip` ### Impact The WF17 E2E test provides zero coverage of the explicit container with directory mount workflow. The container-instance resource type, dual mount registration, execution environment priority override, and precedence resolution are all untested end-to-end. Unlike `tdd_expected_fail` tests (which at least attempt to run and fail), these tests skip entirely, providing no signal about whether the underlying features work. ### Definition of Done The test cases should be implemented with real assertions: 1. `WF17 Explicit Container With Directory Mount Trusted Profile`: Full workflow from resource registration to plan apply 2. `WF17 TDD Dual Mount Registration`: Register container-instance with `--mount resource-ref:rw` and `--mount host-path:ro`, verify both mounts are stored 3. `WF17 TDD Project Level Execution Env Priority Override`: Set `--execution-env-priority override` via `project context set`, verify it persists 4. `WF17 TDD Precedence Level 2 Project Override Resolution`: Verify execution environment resolves via project-level override when no plan-level override is present --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 14:09:07 +00:00

HAL9000 referenced this issue

2026-04-09 15:14:09 +00:00

[AUTO-GROOMER] Backlog Grooming Report (Cycle 63) #6025

HAL9000 added

and removed

labels

2026-04-09 15:14:39 +00:00

HAL9000 commented

2026-04-09 15:21:13 +00:00

Author

Owner

🏷️ Label compliance fix applied by backlog groomer (cycle 64)

Added missing labels: State/Verified, Type/Bug, Priority/High

This issue was missing the State/ and Type/ labels. Labels have been applied based on issue content (UAT-identified WF17 E2E test with all cases unconditionally skipped).

Automated by CleverAgents Bot
Supervisor: Label Management | Agent: forgejo-label-manager

🏷️ **Label compliance fix applied by backlog groomer (cycle 64)** Added missing labels: `State/Verified`, `Type/Bug`, `Priority/High` This issue was missing the `State/` and `Type/` labels. Labels have been applied based on issue content (UAT-identified WF17 E2E test with all cases unconditionally skipped). --- **Automated by CleverAgents Bot** Supervisor: Label Management | Agent: forgejo-label-manager