FastAPI tests: respx mock of the startup data fetch is never used: TestClient(app) without 'with' skips @app.on_event('startup')/lifespan, and module-level caches leak between tests
Fix: enter the client as a context manager inside the active respx mock, and reset module state per test:
@pytest.fixture
def client(monkeypatch, sample_csv):
import app.main as m
monkeypatch.setattr(m, "redis_client", FakeRedis()) # empty cache every test
monkeypatch.setattr(m, "models_data", [])
with respx.mock(assert_all_called=False) as rx:
rx.get(m.INDEX_CSV_URL).mock(return_value=httpx.Response(200, text=sample_csv))
with TestClient(m.app) as c: # runs startup/lifespan here
yield cWhat went wrong in our FastAPI service: the CSV index was fetched with httpx in @app.on_event("startup"), stored in a module global models_data, and also cached in Redis under models_index. The tests built TestClient(app) in a plain fixture and called client.get("/") to "trigger index load". The tests asserted on rows that never appeared, and the respx routes went unused. Three separate causes:
1. Starlette's TestClient only runs startup/shutdown handlers and lifespan when used as with TestClient(app) as client:. A bare instance never calls them, so the loader never ran.
2. respx only intercepts requests sent while the mock is active. A loader that runs at import time or before the respx.mock context starts goes to the real network or does nothing.
3. Once data is cached (module global, Redis, functools.lru_cache), later tests reuse the first test's data whatever their mocks say. Patch the cache to empty for each test, or make the loader a dependency you override with app.dependency_overrides.
Verify: with respx.mock(assert_all_called=True) the test fails if the startup route wasn't hit, which catches regressions in all three.