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>
46 lines
2.2 KiB
Gherkin
46 lines
2.2 KiB
Gherkin
Feature: Execution environment project-level override reaches resolver
|
|
Verifies that project_env threaded through ToolCallRouter
|
|
is forwarded to the ExecutionEnvironmentResolver inside
|
|
ToolRunner.execute(), where it is used at precedence level 2.
|
|
|
|
Issue #1080: execution environment resolution does not honour
|
|
project-level override (precedence level 2).
|
|
|
|
# @tdd_issue @tdd_issue_4248 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: ToolCallRouter forwards project_env to resolver
|
|
Given ee1080- a tool registry with a registered echo tool
|
|
And ee1080- a tool runner and resolver spy
|
|
And ee1080- a ToolCallRouter with project_env "container"
|
|
When ee1080- I route a tool call through the router
|
|
Then ee1080- the resolver should have received project_env "container"
|
|
|
|
# @tdd_issue @tdd_issue_4248 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: ToolCallRouter forwards plan_env to resolver
|
|
Given ee1080- a tool registry with a registered echo tool
|
|
And ee1080- a tool runner and resolver spy
|
|
And ee1080- a ToolCallRouter with plan_env "host"
|
|
When ee1080- I route a tool call through the router
|
|
Then ee1080- the resolver should have received plan_env "host"
|
|
|
|
# @tdd_issue @tdd_issue_4248 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: ToolCallRouter forwards both plan_env and project_env
|
|
Given ee1080- a tool registry with a registered echo tool
|
|
And ee1080- a tool runner and resolver spy
|
|
And ee1080- a ToolCallRouter with both plan_env "host" and project_env "container"
|
|
When ee1080- I route a tool call through the router
|
|
Then ee1080- the resolver should have received plan_env "host"
|
|
And ee1080- the resolver should have received project_env "container"
|
|
|
|
# @tdd_issue @tdd_issue_4248 @tdd_expected_fail @skip
|
|
@skip
|
|
Scenario: ToolCallRouter without env params passes None to resolver
|
|
Given ee1080- a tool registry with a registered echo tool
|
|
And ee1080- a tool runner and resolver spy
|
|
And ee1080- a ToolCallRouter without env params
|
|
When ee1080- I route a tool call through the router
|
|
Then ee1080- the resolver should have received plan_env "None"
|
|
And ee1080- the resolver should have received project_env "None"
|