litellm/tests/e2e/management
mubashir1osmani bfc485b21b test(e2e): fill management P0 coverage gaps and reconcile registry markers
Adds the missing Management/UI P0 e2e tests the coverage registry enumerates but
nothing covered: budget-create persistence read back through /budget/info,
proxy-admin-only enforcement on /budget/new and /team/new, and team-admin-required
enforcement on /team/member_add and /team/member_delete. Each authz test also
asserts the write did not land, so a removed check fails the test rather than
passing on the status code alone

Reconciles the covers markers already on the suite to real registry ids so the
collector counts them instead of flagging orphans: management.team.new.persists to
mgmt.team.new.persists, mgmt.user.new.persists to mgmt.user.new.happy_path,
mgmt.organization.new.persists to mgmt.organization.new.happy_path, and the
route-scoped llm-only-key denial to other.auth.virtual_key.route_permission_enforced,
which is the contract it actually proves. The key-generate test additionally claims
mgmt.key.info.persists and the member add/delete test claims
mgmt.team.member_delete.persists, both of which they already assert

This raises Management/UI P0 coverage from 4/19 to 13/19. The remaining gaps are the
three key.*.admin_only cells (internal users self-serve keys, so "admin_only" is the
wrong framing and needs a registry decision), the SSO-driven key.generate.happy_path,
and the model.* cells handled on the model-management fold branch
2026-07-07 18:59:23 -07:00
..
conftest.py test(e2e): add management suite covering key/team/user/org lifecycle and route permissions (#32300) 2026-07-06 19:11:27 -07:00
management_client.py test(e2e): fill management P0 coverage gaps and reconcile registry markers 2026-07-07 18:59:23 -07:00
test_management_e2e.py test(e2e): fill management P0 coverage gaps and reconcile registry markers 2026-07-07 18:59:23 -07:00