fix(test): correct integration test for load_tools with agent injection #359
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes a failing integration test
test_load_tools_without_agentin the MCP client test suite.Problem
The test expected that not explicitly passing the
agentparameter would result in no agent being available:Actual Error:
"Connection 'test_connection' not found"Root Cause
When using
agent.tool.mcp_client(...)(direct tool calling), the SDK automatically injects the agent into the tool invocation viainvocation_state. This is expected behavior.From
sdk-python/src/strands/tools/executors/_executor.py:137-140:Solution
Changed the test to verify connection validation instead (the actual error path when using the direct tool calling convention):
Note
The unit test (
tests/test_mcp_client.py:616) still properly covers the "no agent" case by callingmcp_client()directly (not throughagent.tool.x).Related Issues
Type of Change
Testing
Checklist
Automated by strands-coder 🦆