test(cli): add Behave scenarios verifying CLI help output sections and V3-only command structure #4379

Open
opened 2026-04-08 11:27:39 +00:00 by HAL9000 · 0 comments
Owner

Metadata

  • Commit Message: test(cli): add Behave scenarios verifying CLI help output sections and V3-only command structure
  • Branch: test/cli-help-output-verification
  • Parent Epic: #4182

Background and Context

Epic #4182 identifies that CLI help output is not tested. After the legacy command removal (#4181) and error message improvements (#4377), the help output structure needs comprehensive Behave test coverage to prevent regressions and verify the V3-only command structure is correctly rendered.

Expected Behavior

Behave scenarios verify:

  • agents plan --help shows only V3 commands (no legacy commands)
  • Help output uses Rich panels with clear visual grouping
  • Deprecation notices are absent (legacy commands removed)
  • All V3 subcommands are present and correctly described
  • Error messages reference only V3 commands

Acceptance Criteria

  • Behave scenarios verify agents plan --help contains V3 command group
  • Behave scenarios verify no legacy commands appear in help output
  • Behave scenarios verify error messages reference V3 commands only
  • Behave scenarios verify help output references migration guide where appropriate
  • All scenarios pass in CI

Supporting Information

  • Key files: src/cleveragents/cli/commands/plan.py, src/cleveragents/cli/formatting.py
  • Test directory: features/ (Behave)
  • Related: #4181 (CLI help output), #4377 (error messages), #4182 (parent epic)
  • Depends on: #4181 (CLI help output separation must be implemented first)

Subtasks

  • Write Behave feature file: features/cli_help_output.feature
  • Scenario: agents plan --help shows V3 Plan Lifecycle section
  • Scenario: agents plan --help does not show legacy commands
  • Scenario: agents plan use --help shows correct V3 arguments
  • Scenario: agents plan execute --help shows correct V3 arguments
  • Scenario: agents plan apply --help shows correct V3 arguments
  • Scenario: error messages when using wrong phase order reference V3 commands only
  • Implement step definitions in features/steps/cli_help_steps.py
  • Run nox (all default sessions), fix any errors
  • Verify coverage >= 97% via nox -s coverage_report

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off.
  • Behave scenarios comprehensively test CLI help output structure.
  • 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 details.
  • 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.
  • All nox stages pass.
  • Coverage >= 97%.

Automated by CleverAgents Bot
Supervisor: Product Builder | Agent: epic-planner

## Metadata - **Commit Message**: `test(cli): add Behave scenarios verifying CLI help output sections and V3-only command structure` - **Branch**: `test/cli-help-output-verification` - **Parent Epic**: #4182 ## Background and Context Epic #4182 identifies that CLI help output is not tested. After the legacy command removal (#4181) and error message improvements (#4377), the help output structure needs comprehensive Behave test coverage to prevent regressions and verify the V3-only command structure is correctly rendered. ## Expected Behavior Behave scenarios verify: - `agents plan --help` shows only V3 commands (no legacy commands) - Help output uses Rich panels with clear visual grouping - Deprecation notices are absent (legacy commands removed) - All V3 subcommands are present and correctly described - Error messages reference only V3 commands ## Acceptance Criteria - [ ] Behave scenarios verify `agents plan --help` contains V3 command group - [ ] Behave scenarios verify no legacy commands appear in help output - [ ] Behave scenarios verify error messages reference V3 commands only - [ ] Behave scenarios verify help output references migration guide where appropriate - [ ] All scenarios pass in CI ## Supporting Information - **Key files**: `src/cleveragents/cli/commands/plan.py`, `src/cleveragents/cli/formatting.py` - **Test directory**: `features/` (Behave) - **Related**: #4181 (CLI help output), #4377 (error messages), #4182 (parent epic) - **Depends on**: #4181 (CLI help output separation must be implemented first) ## Subtasks - [ ] Write Behave feature file: `features/cli_help_output.feature` - [ ] Scenario: `agents plan --help` shows V3 Plan Lifecycle section - [ ] Scenario: `agents plan --help` does not show legacy commands - [ ] Scenario: `agents plan use --help` shows correct V3 arguments - [ ] Scenario: `agents plan execute --help` shows correct V3 arguments - [ ] Scenario: `agents plan apply --help` shows correct V3 arguments - [ ] Scenario: error messages when using wrong phase order reference V3 commands only - [ ] Implement step definitions in `features/steps/cli_help_steps.py` - [ ] Run `nox` (all default sessions), fix any errors - [ ] Verify coverage >= 97% via `nox -s coverage_report` ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - Behave scenarios comprehensively test CLI help output structure. - 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 details. - 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. - All nox stages pass. - Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Product Builder | Agent: epic-planner
HAL9000 added this to the v3.5.0 milestone 2026-04-08 17:42:55 +00:00
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#4379
No description provided.