diff --git a/tests/e2e/coverage_registry/README.md b/tests/e2e/coverage_registry/README.md index 8bf71f7f430..f52856a4125 100644 --- a/tests/e2e/coverage_registry/README.md +++ b/tests/e2e/coverage_registry/README.md @@ -120,7 +120,7 @@ pending. Integration contract IDs belong in `tests/integration/contracts.json`, | Requirement | Existing regression or owning suite | Remaining acceptance and owner | Required before | |---|---|---|---| -| Principal discovery | `mcp/test_mcp_key_access_e2e.py`, `mcp/test_mcp_access_group_e2e.py`, `mcp/test_mcp_toolset_enforcement_e2e.py` | Run key/team/org/user controls on every configured replica; native/REST parity remains LIT-4506 | Phase 0 and affected authorization changes | +| Principal discovery | `mcp/test_mcp_key_access_e2e.py`, `mcp/test_mcp_access_group_e2e.py`, `mcp/test_mcp_toolset_enforcement_e2e.py` | Run key/team/org/user controls on every configured replica; the E2E health check intersects with test-owned servers and proves grant visibility only, non-disclosure of unrelated servers is proven by integration contract other.mcp.health.restricted_keys_intersect_grants_in_both_modes (#41731); native/REST parity remains LIT-4506 | Phase 0 and affected authorization changes | | No self-attached unauthorized grants | Management key authorization tests | Read back unchanged server/toolset/access-group grants after rejected writes, LIT-4502 | Affected grant capability activation | | UI/API parity | Admin MCP UI suite | Same non-admin actor and permissions across both surfaces, LIT-3644 / LIT-4506 | Affected UI capability activation | | Server identity routing | Saved-server lifecycle integration and resolver tests | Cold routing, duplicate/unprefixed names, LIT-4500 | Routing changes | diff --git a/tests/e2e/mcp/datadog_mcp.py b/tests/e2e/mcp/datadog_mcp.py index 352b4446cfd..e16f62d7be6 100644 --- a/tests/e2e/mcp/datadog_mcp.py +++ b/tests/e2e/mcp/datadog_mcp.py @@ -1,4 +1,9 @@ -"""Shared helpers for e2e tests that register the real Datadog remote MCP server.""" +"""Shared helpers for e2e tests that register the real Datadog remote MCP server. + +The search_datadog_logs arguments these suites send (query, from, to, max_tokens) come from +https://docs.datadoghq.com/mcp_server/tools/ (checked 2026-09-19). McpToolEntry.assert_arguments_are_documented +compares them with the schema the gateway advertises live, so a failure there after a Datadog rename is stale, +not broken litellm code""" from __future__ import annotations