mirror of https://github.com/meta-llama/llama-stack.git synced 2025-07-31 08:00:09 +00:00

History

Matthew Farrellee 968fc132d3 fix(openai-compat): restrict developer/assistant/system/tool messages to text-only content (#2932 ) What: - Added OpenAIChatCompletionTextOnlyMessageContent type for text-only content validation - Modified OpenAISystemMessageParam, OpenAIAssistantMessageParam, OpenAIDeveloperMessageParam, and OpenAIToolMessageParam to use text-only content type instead of mixed content - OpenAIUserMessageParam unchanged - still accepts both text and images - Updated OpenAPI spec files to reflect text-only content restrictions in schemas closes #2894 Why: - Enforces OpenAI API compatibility by restricting image content to user messages only - Prevents API misuse where images might be sent in message types that don't support them - Aligns with OpenAI's actual API behavior where only user messages can contain multimodal content - Improves type safety and validation at the API boundary Test plan: - Added comprehensive parametrized tests covering all 5 OpenAI message types - Tests verify text string acceptance for all message types - Tests verify text list acceptance for all message types - Tests verify image rejection for system/assistant/developer/tool messages (ValidationError expected) - Tests verify user messages still accept images (backward compatibility maintained)		2025-07-28 10:36:34 -07:00
..
cli	fix: stop image_name from being cast to an integer (#2759 )	2025-07-15 09:44:21 -07:00
distribution	fix: Fix unit tests CI and failing tests (#2928 )	2025-07-28 10:07:26 -07:00
files	feat: enable auth for LocalFS Files Provider (#2773 )	2025-07-18 19:11:01 -07:00
models	chore(test): migrate unit tests from unittest to pytest for system prompt (#2789 )	2025-07-18 11:54:02 +02:00
providers	fix(openai-compat): restrict developer/assistant/system/tool messages to text-only content (#2932 )	2025-07-28 10:36:34 -07:00
rag	fix: search mode validation for rag query (#2857 )	2025-07-23 11:25:12 -07:00
registry	chore: default to pytest asyncio-mode=auto (#2730 )	2025-07-11 13:00:24 -07:00
server	fix: Fix unit tests CI and failing tests (#2928 )	2025-07-28 10:07:26 -07:00
utils	chore: default to pytest asyncio-mode=auto (#2730 )	2025-07-11 13:00:24 -07:00
__init__.py	chore: Add fixtures to conftest.py (#2067 )	2025-05-06 13:57:48 +02:00
conftest.py	chore: block network access from unit tests (#2732 )	2025-07-12 16:53:54 -07:00
fixtures.py	chore: default to pytest asyncio-mode=auto (#2730 )	2025-07-11 13:00:24 -07:00
README.md	test: Measure and track code coverage (#2636 )	2025-07-18 18:08:36 +02:00

README.md

Llama Stack Unit Tests

Unit Tests

Unit tests verify individual components and functions in isolation. They are fast, reliable, and don't require external services.

Prerequisites

Python Environment: Ensure you have Python 3.12+ installed
uv Package Manager: Install uv if not already installed

You can run the unit tests by running:

./scripts/unit-tests.sh [PYTEST_ARGS]

Any additional arguments are passed to pytest. For example, you can specify a test directory, a specific test file, or any pytest flags (e.g., -vvv for verbosity). If no test directory is specified, it defaults to "tests/unit", e.g:

./scripts/unit-tests.sh tests/unit/registry/test_registry.py -vvv

If you'd like to run for a non-default version of Python (currently 3.12), pass PYTHON_VERSION variable as follows:

source .venv/bin/activate
PYTHON_VERSION=3.13 ./scripts/unit-tests.sh

Test Configuration

Test Discovery: Tests are automatically discovered in the tests/unit/ directory
Async Support: Tests use --asyncio-mode=auto for automatic async test handling
Coverage: Tests generate coverage reports in htmlcov/ directory
Python Version: Defaults to Python 3.12, but can be overridden with PYTHON_VERSION environment variable

Coverage Reports

After running tests, you can view coverage reports:

# Open HTML coverage report in browser
open htmlcov/index.html  # macOS
xdg-open htmlcov/index.html  # Linux
start htmlcov/index.html  # Windows