freemo
8ea00f5185
CI / unit_tests (push) Has been cancelled
CI / benchmark-publish (push) Has been cancelled
CI / lint (push) Has been cancelled
CI / typecheck (push) Has been cancelled
CI / security (push) Has been cancelled
CI / quality (push) Has been cancelled
CI / integration_tests (push) Has been cancelled
CI / e2e_tests (push) Has been cancelled
CI / coverage (push) Has been cancelled
CI / benchmark-regression (push) Has been cancelled
CI / build (push) Has been cancelled
CI / push-validation (push) Has been cancelled
CI / status-check (push) Has been cancelled
CI / docker (push) Has been cancelled
CI / helm (push) Has been cancelled
Co-authored-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me> Co-committed-by: Jeffrey Phillips Freeman <the@jeffreyfreeman.me>
68 lines
2.4 KiB
Gherkin
68 lines
2.4 KiB
Gherkin
Feature: Actor CLI YAML-first alignment
|
|
As a developer
|
|
I want actor CLI commands aligned to YAML-first configs
|
|
So that actors can be managed with namespaced names and multiple output formats
|
|
|
|
Scenario: Actor list outputs JSON format
|
|
Given an actor CLI runner
|
|
When I run actor list with two actors using format json
|
|
Then the actor list output should be valid JSON
|
|
|
|
Scenario: Actor list outputs YAML format
|
|
Given an actor CLI runner
|
|
When I run actor list with two actors using format yaml
|
|
Then the actor list output should contain YAML keys
|
|
|
|
Scenario: Actor list outputs plain format
|
|
Given an actor CLI runner
|
|
When I run actor list with two actors using format plain
|
|
Then the actor list output should contain plain text fields
|
|
|
|
Scenario: Actor show outputs JSON format
|
|
Given an actor CLI runner
|
|
When I run actor show with format json
|
|
Then the actor show output should be valid JSON with actor fields
|
|
|
|
Scenario: Actor show outputs YAML format
|
|
Given an actor CLI runner
|
|
When I run actor show with format yaml
|
|
Then the actor show output should contain YAML actor keys
|
|
|
|
Scenario: Actor show outputs plain format
|
|
Given an actor CLI runner
|
|
When I run actor show with format plain
|
|
Then the actor show output should contain plain actor fields
|
|
|
|
Scenario: Actor add with update flag
|
|
Given an actor CLI runner
|
|
And I have an actor JSON config file
|
|
When I run actor add with update flag
|
|
Then the actor add should pass the loaded config
|
|
And the output should say Actor updated
|
|
|
|
# @tdd_issue @tdd_issue_4233 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: Actor add outputs JSON format
|
|
Given an actor CLI runner
|
|
And I have an actor JSON config file
|
|
When I run actor add with format json
|
|
Then the actor add output should contain JSON data
|
|
|
|
# @tdd_issue @tdd_issue_4233 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: Actor add with YAML config file and format
|
|
Given an actor CLI runner
|
|
And I have an actor YAML-only config file
|
|
When I run actor add with format yaml
|
|
Then the actor add output should contain YAML data
|
|
|
|
Scenario: Actor remove by namespaced name
|
|
Given an actor CLI runner
|
|
When I run actor remove with namespaced name
|
|
Then the actor remove should succeed for namespaced name
|
|
|
|
Scenario: Actor update outputs JSON format
|
|
Given an actor CLI runner
|
|
When I run actor update with format json
|
|
Then the actor update output should contain JSON data
|