Ashwin Bharambe 40b11efac4 feat(tests): add TypeScript client integration test support (#4185) ... 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 ```		2025-11-19 10:07:53 -08:00
..
install-llama-stack-client	fix(ci): use test.pypi as extra index for RC dependencies (#4009)	2025-10-31 12:55:43 -07:00
run-and-record-tests	ci: Add vLLM support to integration testing infrastructure (with qwen) (#3545)	2025-11-06 10:36:40 +01:00
setup-ollama	feat(tests): migrate to global "setups" system for test configuration (#3390)	2025-09-09 15:50:56 -07:00
setup-runner	fix(ci): export UV_INDEX_STRATEGY to current shell before running uv sync (#4020)	2025-11-01 12:57:24 -07:00
setup-test-environment	fix: harden storage semantics (#4118)	2025-11-12 10:35:39 -08:00
setup-typescript-client	feat(tests): add TypeScript client integration test support (#4185)	2025-11-19 10:07:53 -08:00
setup-vllm	ci: Add vLLM support to integration testing infrastructure (with qwen) (#3545)	2025-11-06 10:36:40 +01:00