test: add LiteLLM Proxy runtime smoke test#31
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 an opt-in Tier 2 runtime smoke test for the LiteLLM Proxy reference integration.
The test launches a real LiteLLM Proxy subprocess, loads the existing Context Compiler pre-call hook, sends requests through /v1/chat/completions, and verifies blocking and forwarding behavior against a local OpenAI-compatible stub upstream.
Why
Existing LiteLLM Proxy tests covered hook behavior directly, but did not prove that the real proxy runtime could:
This adds opt-in runtime evidence for the most important remaining LiteLLM Proxy gap tracked by issue #13.
Changes
Scope
This PR does not:
Notes
The runtime smoke test is opt-in:
RUN_LITELLM_PROXY_RUNTIME=1 uv run --group proxy_runtime pytest python/tests/test_litellm_proxy_runtime.py
The test uses a local OpenAI-compatible stub upstream rather than a live model provider.
Issue #13 impact
This partially addresses issue #13 by adding automated runtime coverage for LiteLLM Proxy startup, hook loading, request blocking/forwarding, and teardown.
Issue #13 should remain open until maintainers decide whether this satisfies the LiteLLM Proxy runtime requirement and until the remaining OpenWebUI or other runtime validation gaps are reviewed.