HAL9000
195fbac109
CI / lint (pull_request) Successful in 40s
CI / helm (pull_request) Successful in 38s
CI / build (pull_request) Successful in 48s
CI / quality (pull_request) Successful in 1m0s
CI / typecheck (pull_request) Successful in 1m29s
CI / security (pull_request) Successful in 1m28s
CI / push-validation (pull_request) Successful in 20s
CI / unit_tests (pull_request) Successful in 5m8s
CI / docker (pull_request) Successful in 1m27s
CI / integration_tests (pull_request) Successful in 8m39s
CI / coverage (pull_request) Successful in 11m1s
CI / status-check (pull_request) Successful in 3s
Add domain-scenario Gherkin tags to all A2A, session, and CLI feature files (30 files) so tests can be filtered individually via behave. - 8 A2A feature files: @a2a tag - 7 session feature files: @session tag - 15 CLI feature files: @cli tag ISSUES CLOSED: #9124
30 lines
1.4 KiB
Gherkin
30 lines
1.4 KiB
Gherkin
@cli
|
|
Feature: CLI lifecycle Robot alignment
|
|
As a developer
|
|
I want a Behave scenario mirroring the Robot E2E lifecycle flow
|
|
So that unit and integration test expectations stay aligned
|
|
|
|
Background:
|
|
Given a robot alignment CLI runner
|
|
And a robot alignment mocked lifecycle service
|
|
|
|
Scenario: Full lifecycle action to apply with changeset verification
|
|
Given a robot alignment action "local/lifecycle-action" is created via config
|
|
When I run robot alignment plan use "local/lifecycle-action" on project "proj-a"
|
|
Then the robot alignment plan use should succeed
|
|
When I run robot alignment plan execute for the plan
|
|
Then the robot alignment plan execute should succeed
|
|
And the robot alignment changeset should have 1 entry with operation "create"
|
|
When I run robot alignment plan apply for the plan
|
|
Then the robot alignment plan apply should succeed
|
|
And the robot alignment changeset summary should have total 2
|
|
|
|
Scenario: Invalid arg format rejected via CLI
|
|
Given a robot alignment action "local/lifecycle-action" exists
|
|
When I run robot alignment plan use with invalid arg "bad_arg_no_equals"
|
|
Then the robot alignment CLI should reject the invalid arg format
|
|
|
|
Scenario: Missing action returns error via CLI
|
|
When I run robot alignment plan use for nonexistent action "local/nonexistent"
|
|
Then the robot alignment CLI should report action not found
|