UAT: tdd_exec_env_resolution_precedence.feature references closed issue #1080 but entire feature is @skip — stale TDD test needs cleanup #5648

New issue

Open

opened 2026-04-09 08:05:18 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 08:05:18 +00:00

Owner

Background and Context

CONTRIBUTING.md states under Bug Fix Workflow:

When a bug is fixed, the @tdd_expected_fail tag must be removed so the test runs normally as a regression guard.

Issue #1080 ("bug(cli): execution environment resolution does not honour project-level override") is closed, meaning the bug was fixed. However, features/tdd_exec_env_resolution_precedence.feature still exists with all scenarios tagged @skip and the @tdd_expected_fail tags commented out.

Current Behavior

features/tdd_exec_env_resolution_precedence.feature:

Feature-level tag: @skip (entire feature is skipped)
References closed issue #1080
All scenarios are @skip
@tdd_expected_fail tags are commented out (prefixed with #)

This means:

The bug fix regression tests are NOT running (all scenarios are @skip)
The feature is dead code that provides no test coverage
The @skip tag was likely added as a workaround but never cleaned up after the fix

Expected Behavior

When a bug is fixed:

The @tdd_expected_fail tag should be removed
The @skip tag should be removed
The scenarios should run normally as regression guards

Acceptance Criteria

features/tdd_exec_env_resolution_precedence.feature is either:
- Cleaned up: @skip removed, scenarios run as regression guards, OR
- Deleted: if the scenarios are already covered by other tests
No @skip scenarios exist for closed issues without explanation

Supporting Information

Issue #1080 state: closed
Feature file: features/tdd_exec_env_resolution_precedence.feature
All 3 scenarios have @skip tag
Feature-level comment: # @tdd_issue @tdd_issue_1080 @tdd_expected_fail @tdd_issue_4178 @mock_only @skip

Metadata

Commit Message: fix(tests): clean up stale tdd_exec_env_resolution_precedence feature — remove @skip after #1080 fix
Branch: fix/cleanup-stale-tdd-exec-env

Subtasks

Verify issue #1080 fix is complete and working
Remove @skip from scenarios in tdd_exec_env_resolution_precedence.feature
Remove commented-out @tdd_expected_fail tags
Verify scenarios pass without @tdd_expected_fail

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created with the prescribed commit message.
The commit is pushed to the branch and submitted as a pull request to master, reviewed, and merged.

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

## Background and Context CONTRIBUTING.md states under **Bug Fix Workflow**: > When a bug is fixed, the `@tdd_expected_fail` tag must be removed so the test runs normally as a regression guard. Issue #1080 ("bug(cli): execution environment resolution does not honour project-level override") is **closed**, meaning the bug was fixed. However, `features/tdd_exec_env_resolution_precedence.feature` still exists with all scenarios tagged `@skip` and the `@tdd_expected_fail` tags commented out. ## Current Behavior `features/tdd_exec_env_resolution_precedence.feature`: - Feature-level tag: `@skip` (entire feature is skipped) - References closed issue #1080 - All scenarios are `@skip` - `@tdd_expected_fail` tags are commented out (prefixed with `#`) This means: 1. The bug fix regression tests are NOT running (all scenarios are `@skip`) 2. The feature is dead code that provides no test coverage 3. The `@skip` tag was likely added as a workaround but never cleaned up after the fix ## Expected Behavior When a bug is fixed: 1. The `@tdd_expected_fail` tag should be removed 2. The `@skip` tag should be removed 3. The scenarios should run normally as regression guards ## Acceptance Criteria - [ ] `features/tdd_exec_env_resolution_precedence.feature` is either: - Cleaned up: `@skip` removed, scenarios run as regression guards, OR - Deleted: if the scenarios are already covered by other tests - [ ] No `@skip` scenarios exist for closed issues without explanation ## Supporting Information - Issue #1080 state: **closed** - Feature file: `features/tdd_exec_env_resolution_precedence.feature` - All 3 scenarios have `@skip` tag - Feature-level comment: `# @tdd_issue @tdd_issue_1080 @tdd_expected_fail @tdd_issue_4178 @mock_only @skip` ## Metadata - **Commit Message**: `fix(tests): clean up stale tdd_exec_env_resolution_precedence feature — remove @skip after #1080 fix` - **Branch**: `fix/cleanup-stale-tdd-exec-env` ## Subtasks - [ ] Verify issue #1080 fix is complete and working - [ ] Remove `@skip` from scenarios in `tdd_exec_env_resolution_precedence.feature` - [ ] Remove commented-out `@tdd_expected_fail` tags - [ ] Verify scenarios pass without `@tdd_expected_fail` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created with the prescribed commit message. - The commit is pushed to the branch and submitted as a pull request to `master`, reviewed, and merged. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 added the

labels

2026-04-09 08:05:54 +00:00

HAL9000 added a new dependency