Jeff (CTO)
d98666651f
CI / lint (pull_request) Successful in 15s
CI / typecheck (pull_request) Successful in 27s
CI / security (pull_request) Successful in 22s
CI / quality (pull_request) Successful in 15s
CI / integration_tests (pull_request) Successful in 4m24s
CI / build (pull_request) Successful in 16s
CI / unit_tests (pull_request) Successful in 9m27s
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / coverage (pull_request) Successful in 6m55s
CI / docker (pull_request) Successful in 39s
- Enforce config-only 'action create --config <file>' (remove legacy inline flags: --name, --strategy-actor, --execution-actor, --definition-of-done, --arg) - Load config via ActionConfigSchema.from_yaml_file() then Action.from_config() with clear validation error surfacing - Remove 'action available' subcommand (no draft state; actions are available by default) - Add REGEX positional arg to 'action list' for name filtering - Add Short Name and Definition of Done summary to all CLI outputs - Add 'action list --namespace/-n' and '--state/-s' filters - Update existing tests to match new config-only create flow - Add features/action_cli_spec_alignment.feature (19 scenarios) - Add robot/action_cli_spec.robot smoke tests - Add benchmarks/action_cli_bench.py ASV benchmarks - Add docs/reference/action_cli.md
41 lines
1.6 KiB
Gherkin
41 lines
1.6 KiB
Gherkin
Feature: Action CLI uncovered lines coverage
|
|
As a developer
|
|
I want to exercise action CLI error paths
|
|
So that action.py uncovered lines are executed
|
|
|
|
Background:
|
|
Given an action CLI runner with mocks
|
|
And a mocked plan lifecycle service
|
|
|
|
# Create error handling (config-only)
|
|
Scenario: Create action surfaces validation errors from the service
|
|
Given a valid action config YAML file
|
|
When I run action CLI create with validation error from service
|
|
Then the action CLI should abort with validation error
|
|
|
|
Scenario: Create action surfaces service errors from the lifecycle service
|
|
Given a valid action config YAML file
|
|
When I run action CLI create with service error from config
|
|
Then the action CLI should abort with service error
|
|
|
|
# List invalid state handling
|
|
Scenario: List actions rejects unsupported state filter
|
|
When I run action CLI list with invalid state "unsupported"
|
|
Then the action CLI should abort with invalid state
|
|
|
|
# List error handling
|
|
Scenario: List actions surfaces lifecycle service errors
|
|
When I run action CLI list with service error
|
|
Then the action CLI should abort with service error
|
|
|
|
# Show error handling
|
|
Scenario: Show action surfaces lifecycle service errors
|
|
When I run action CLI show with service error
|
|
Then the action CLI should abort with service error
|
|
|
|
# Archive service error handling
|
|
Scenario: Archive command surfaces lifecycle service errors
|
|
Given there is a mocked available action
|
|
When I run action CLI archive with service error
|
|
Then the action CLI should abort with service error
|