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
68 lines
3.0 KiB
Gherkin
68 lines
3.0 KiB
Gherkin
@a2a
|
|
@mock_only
|
|
Feature: A2A extension method routing via _cleveragents/ prefix
|
|
As a CleverAgents developer
|
|
I want the A2A local facade to support _cleveragents/ extension methods
|
|
So that operations use spec-aligned method names per ADR-047
|
|
|
|
Scenario: Facade supports all _cleveragents/ extension operations
|
|
Given a facade instance for extension method testing
|
|
Then the facade should support _cleveragents/plan/ methods
|
|
And the facade should support _cleveragents/registry/ methods
|
|
And the facade should support _cleveragents/context/ methods
|
|
And the facade should support _cleveragents/health/ methods
|
|
And the facade should support _cleveragents/sync/ methods
|
|
And the facade should support _cleveragents/namespace/ methods
|
|
|
|
Scenario: Plan use via _cleveragents/plan/use
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/plan/use" with params {"action_name": "test"}
|
|
Then the response should be ok
|
|
And the response data should contain key "plan_id"
|
|
|
|
Scenario: Plan execute via _cleveragents/plan/execute
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/plan/execute" with params {"plan_id": "test-id"}
|
|
Then the response should be ok
|
|
|
|
Scenario: Plan cancel via _cleveragents/plan/cancel
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/plan/cancel" with params {"plan_id": "test-id"}
|
|
Then the response should be ok
|
|
|
|
Scenario: Plan list via _cleveragents/plan/list
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/plan/list" with params {}
|
|
Then the response should be ok
|
|
And the response data should contain key "plans"
|
|
|
|
Scenario: Health check via _cleveragents/health/check
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/health/check" with params {}
|
|
Then the response should be ok
|
|
And the response data should contain key "status"
|
|
|
|
Scenario: Sync stub returns not_implemented
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/sync/pull" with params {}
|
|
Then the response should be ok
|
|
And the response data should have "stub" set to true
|
|
|
|
Scenario: Namespace stub returns not_implemented
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/namespace/list" with params {}
|
|
Then the response should be ok
|
|
And the response data should have "stub" set to true
|
|
|
|
Scenario: Legacy operation names still work
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "plan.create" with params {"action_name": "test"}
|
|
Then the response should be ok
|
|
And the response data should contain key "plan_id"
|
|
|
|
Scenario: Registry tool list via extension method
|
|
Given a facade instance for extension method testing
|
|
When I dispatch "_cleveragents/registry/tool/list" with params {}
|
|
Then the response should be ok
|
|
And the response data should contain key "tools"
|