mirror of
https://github.com/BerriAI/litellm.git
synced 2026-10-12 03:48:56 +00:00
048a1500df
* test(e2e): move the harness self-tests out of tests/e2e The nightly Buildkite run copies tests/e2e into the runner image and runs bare pytest, so the 672 tests of the harness itself (fixture parsing, JUnit properties, the stack lock, the load aggregators, the Claude Code driver) counted as e2e tests on the status page even though none of them reaches a proxy. They now live in tests/e2e_harness, mirroring the tests/e2e layout, and run in the GitHub Actions lint job and the CircleCI provider_replay_harness job instead * fix(ci): point the providers replay controls at tests/e2e_harness The providers integration job still selected the four replay-control tests under tests/e2e/test_provider_edge.py, so pytest exited before they ran. The raw-HTTP check's file walk also drops to one loop per comprehension * style(tests): mark the raw-HTTP check's bindings Final
9 lines
643 B
INI
9 lines
643 B
INI
[pytest]
|
|
# Tests of the tests/e2e harness itself. They import harness modules by bare name
|
|
# (`from e2e_http import ...`, `from batch_cleanup import ...`) exactly as the suites
|
|
# do, so tests/e2e and each suite folder that owns a module under test go on the path.
|
|
addopts = --strict-markers --strict-config -p no:cacheprovider
|
|
pythonpath = ../e2e ../e2e/batches ../e2e/guardrails ../e2e/load ../e2e/logging
|
|
markers =
|
|
covers(cell_id, *, exercised_on=()): coverage-registry cell(s) a test covers; exercised here only to prove the collector and the JUnit properties read it
|
|
cli_determinism: drives the real claude CLI for several seconds
|