mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-12-03 09:53:45 +00:00
40b11efac4
Integration tests can now validate the TypeScript SDK alongside Python tests when running against server-mode stacks. Currently, this only adds a _small_ number of tests. We should extend only if truly needed -- this smoke check may be sufficient. When `RUN_CLIENT_TS_TESTS=1` is set, the test script runs TypeScript tests after Python tests pass. Tests are mapped via `tests/integration/client-typescript/suites.json` which defines which TypeScript test files correspond to each Python suite/setup combination. The fact that we need exact "test_id"s (which are actually generated by pytest) to be hardcoded inside the Typescript tests (so we hit the recorded paths) is a big smell and it might become grating, but maybe the benefit is worth it if we keep this test suite _small_ and targeted. ## Test Plan Run with TypeScript tests enabled: ```bash OPENAI_API_KEY=dummy RUN_CLIENT_TS_TESTS=1 \ scripts/integration-tests.sh --stack-config server:ci-tests --suite responses --setup gpt ``` |
||
|---|---|---|
| .. | ||
| github | ||
| openapi_generator | ||
| telemetry | ||
| check-init-py.sh | ||
| check-workflows-use-hashes.sh | ||
| cleanup_recordings.py | ||
| diagnose_recordings.py | ||
| distro_codegen.py | ||
| docker.sh | ||
| gen-changelog.py | ||
| gen-ci-docs.py | ||
| generate_ci_matrix.py | ||
| generate_prompt_format.py | ||
| get_setup_env.py | ||
| install.sh | ||
| integration-tests.sh | ||
| normalize_recordings.py | ||
| provider_codegen.py | ||
| run-ui-linter.sh | ||
| run_openapi_generator.sh | ||
| unit-tests.sh | ||
| uv-run-with-index.sh | ||