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
47 lines
1.9 KiB
Gherkin
47 lines
1.9 KiB
Gherkin
@a2a
|
|
@mock_only
|
|
Feature: A2A CLI facade integration
|
|
As a CleverAgents developer
|
|
I want CLI commands to route through the A2A local facade
|
|
So that all operations comply with the A2A protocol data flow
|
|
|
|
Scenario: CLI bootstrap creates a wired facade
|
|
Given a facade created via the CLI bootstrap
|
|
Then the facade should support all 42 operations
|
|
And the facade should be cached on subsequent calls
|
|
|
|
Scenario: Session create routes through facade
|
|
Given a facade with a mock session service
|
|
When I dispatch a session.create operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan create routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.create operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan execute routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.execute operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan apply routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.apply operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan status routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.status operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Plan diff routes through facade
|
|
Given a facade with a mock plan lifecycle service
|
|
When I dispatch a plan.diff operation via the CLI facade helper
|
|
Then the facade should return an ok response
|
|
|
|
Scenario: Facade notification is best-effort
|
|
Given a facade that raises an error on dispatch
|
|
When I call the plan notify_facade helper with operation "plan.create"
|
|
Then no exception should propagate to the caller
|