forked from HAL9000/cleveragents-core
8ea00f5185
Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>
27 lines
1.2 KiB
Gherkin
27 lines
1.2 KiB
Gherkin
Feature: agents actor add NAME positional argument
|
|
As a user of the CleverAgents CLI
|
|
I want to pass the actor name as a positional argument to `agents actor add`
|
|
So that the CLI matches the spec synopsis: agents actor add <NAME> --config <FILE>
|
|
|
|
# @tdd_issue @tdd_issue_4230 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: actor add accepts NAME as positional argument
|
|
Given an actor CLI runner
|
|
And I have an actor JSON config file without a name field
|
|
When I run actor add with NAME positional argument and config
|
|
Then the actor add should succeed with the positional name
|
|
|
|
# @tdd_issue @tdd_issue_4230 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: actor add NAME positional argument takes precedence over config name
|
|
Given an actor CLI runner
|
|
And I have an actor JSON config file with a different name
|
|
When I run actor add with NAME positional argument overriding config name
|
|
Then the actor add should use the positional NAME not the config name
|
|
|
|
Scenario: actor add without NAME positional argument fails
|
|
Given an actor CLI runner
|
|
And I have an actor JSON config file without a name field
|
|
When I run actor add with config but no NAME positional argument
|
|
Then the actor command should fail with missing argument error
|