Skip to content

Conversation

TeddyAmkie
Copy link
Collaborator

Relevant issues

Initial PR for E2E testing of main routes and providers.

test_e2e_azure_batches.py - Azure Batches API validation
test_e2e_azure_chat_completions.py - Chat completions testing
test_e2e_azure_messages.py - Messages API functionality
test_e2e_azure_responses.py - Response format validation

Configuration & Documentation

azure_testing_config.yaml - LiteLLM proxy configuration for Azure
run_e2e_tests.sh - Main test runner script (improved in this PR)
README.md - Setup instructions and usage guide
E2E_Testing_Q4_2025_Roadmap.md - Testing roadmap and planned enhancements

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
Screenshot 2025-08-25 at 6 28 38 PM

Type

📖 Documentation
🚄 Infrastructure
✅ Test

Changes

TeddyAmkie and others added 4 commits August 24, 2025 22:05
- Complete test coverage for all 4 Azure endpoints (/chat/completions, /messages, /responses, /batches)
- 24 tests passing with full validation of OpenAI schema compliance
- Automated test runner with environment setup and proxy management
- Updated E2E testing roadmap marking Azure OpenAI as completed ✅
- Configured o4-mini model for Azure Responses API with 2025-03-01-preview
- Comprehensive error handling and edge case testing
- Ready for CI/CD integration
…test files

- Replace hardcoded personal path with dynamic detection using BASH_SOURCE
- Script now works for any user's litellm repository location
- Move Azure test files from tests/azure_endpoints_tests/ to tests/openai_endpoints_tests/azure_endpoints_tests/
- Maintain proper directory structure for better organization
- Update AZURE_API_MODEL to use gpt-4.1 instead of gpt-4
- Configure all model aliases to use azure/gpt-4.1 deployment (except responses API)
- Keep o4-mini for responses API tests only
- Update max_tokens to 150+ across all tests for better token allocation
- Switch API version to 2024-10-01-preview for GPT-4.1 compatibility
- Fix streaming and function calling test compatibility with standard GPT behavior
Copy link

vercel bot commented Aug 26, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
litellm Ready Ready Preview Comment Aug 28, 2025 0:40am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant