test: add LiteLLM schema selection runtime coverage#30
Merged
Conversation
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.
Summary
Adds Tier 2 runtime-boundary coverage for the existing Python LiteLLM response_format schema-selection example.
The new tests exercise the real litellm.completion(...) call path against a local OpenAI-compatible stub server and assert on the actual HTTP payload received by the stub.
Why
The existing schema-selection coverage verified host-side selection behavior, but did not prove that the selected response_format crossed a real LiteLLM runtime boundary.
This change validates that schema selection affects the actual LiteLLM request payload without requiring an OpenAI, Anthropic, or other frontier-model key.
Changes
Scope
This PR does not:
Notes
The tests use an ephemeral localhost OpenAI-compatible stub server. They verify:
Tier 2 Coverage Impact
This closes the schema-selection runtime-boundary gap identified during the Tier 2 audit.