test: Restore responses unit tests#4153
Merged
ashwinb merged 6 commits intollamastack:mainfrom Nov 14, 2025
Merged
Conversation
ashwinb
requested changes
Nov 13, 2025
Contributor
ashwinb
left a comment
There was a problem hiding this comment.
Uh oh, looks like the tests rotted a bit so we need to fix them. Do you want to do that or do you want me to look into that?
Contributor
Author
|
Ah I see. There was some restructuring that went in right before my PR. I'll take a first stab at fixing the tests. |
…ama-stack into restore_responses_unit_tests
ashwinb
approved these changes
Nov 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Restores the responses unit tests that were inadvertently deleted in PR #4055
Test Plan
I ran the unit tests that I restored. They all passed with one exception:
It's coming from this line:
The mcp.py module (and __init__.py) exists under tools. There are some 'from mcp ....' imports (mcp package in this case) within it that python may be interpreting as circular imports (or maybe I'm overlooking something).