scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-09-20 00:11:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 75

docs(e2e): name the e2e-dev group in the documented suite run commands

Browse source 
The llm_translation suite needs the e2e-dev dependency group at collection
time (websockets for the realtime folder, now also the anthropic SDK for the
sdk fixture). make bootstrap installs the group, but the documented pytest
command did not name it, so a default dev-group environment failed collection.
Naming the group on uv run makes the command work from any environment state
This commit is contained in:
mateo-berri 2026-07-23 06:32:29 +00:00
parent 76bf0cd579
commit 0e34c18d7e
No known key found for this signature in database
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
tests/e2e/CONTRIBUTING.md
View file

@ -35,10 +35,10 @@ The suites run against a live proxy, so bring one up first by running the litell
curl -fs http://localhost:4000/health/liveliness
```
4. Run a suite against it; the harness reads `LITELLM_PROXY_URL` (default `http://localhost:4000`):
4. Run a suite against it; the harness reads `LITELLM_PROXY_URL` (default `http://localhost:4000`). The suites' client dependencies (the provider SDKs, websockets) live in the `e2e-dev` dependency group; `make bootstrap` installs it, and naming the group on the run keeps the command working from any environment state:
```bash
uv run pytest tests/e2e/llm_translation/ -v
uv run --group e2e-dev pytest tests/e2e/llm_translation/ -v
```
The browser tests in the `management/` suite drive the dashboard the proxy serves at `/ui` through playwright, an optional dependency behind `importorskip` (the suite's API tests run without it). It lives in the `e2e-dev` dependency group; install it along with its browser:
@ -148,7 +148,7 @@ Before you push
```bash
litellm --config <your-e2e-config>.yml --port 4000
uv run pytest tests/e2e/<your_suite>/ -v
uv run --group e2e-dev pytest tests/e2e/<your_suite>/ -v
```
4. Capture screenshots of the test run and attach them to the PR as proof