llama-stack-mirror/.github
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
..
actions feat(tests): add TypeScript client integration test support (#4185) 2025-11-19 10:07:53 -08:00
ISSUE_TEMPLATE docs: fix broken links (#3647) 2025-10-01 16:48:13 -07:00
workflows feat(tests): add TypeScript client integration test support (#4185) 2025-11-19 10:07:53 -08:00
CODEOWNERS chore: Remove myself from codeowners (#4175) 2025-11-17 09:28:41 -05:00
dependabot.yml chore: move src/llama_stack/ui to src/llama_stack_ui (#4068) 2025-11-04 15:21:49 -08:00
mergify.yml ci: introduce Mergify bot to notify on PR conflicts (#4043) 2025-11-03 12:21:19 -08:00
PULL_REQUEST_TEMPLATE.md chore: fix visible comments in pr template (#2279) 2025-05-27 15:42:33 +02:00
TRIAGERS.md chore: update CODEOWNERS (#3613) 2025-10-03 17:12:34 -07:00