Skip to content

test: add cloud-dev e2e test skeleton + CI wiring for mongodb-mcp-remote (MCP-538)#1271

Draft
maastha wants to merge 1 commit into
MCP-538from
MCP-538-e2e
Draft

test: add cloud-dev e2e test skeleton + CI wiring for mongodb-mcp-remote (MCP-538)#1271
maastha wants to merge 1 commit into
MCP-538from
MCP-538-e2e

Conversation

@maastha

@maastha maastha commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

Summary
Stacked on #1268. Adds the cloud-dev e2e test for the remote MCP wrapper — the skeleton and CI plumbing. The actual test will be implemented in MCP-539 (and need the wrapper from MCP-536), so this is safe to merge on its own.

Changes

  • Adds an e2e test that targets the real cloud-dev Remote MCP server, self-skips unless credentials are provided.
  • Wires CI to inject the e2e credentials from GitHub secrets (dedicated env-var names).

Out of scope: e2e test bodies (MCP-539), wrapper implementation (MCP-536).

Ticket: MCP-538

Checklist

…MCP-538)

Stack the real cloud-dev e2e tier on the unit/integration setup:

- wrapper.e2e.test.ts: runs in the normal suite but self-skips via describe.skipIf
  unless MDB_MCP_REMOTE_E2E_CLIENT_ID is set (and on SKIP_REMOTE_MCP_E2E=true).
  Bodies are it.todo for MCP-539 against the real wrapper (MCP-536).
- code-health.yml run-tests: inject MDB_MCP_REMOTE_E2E_* from dedicated
  TEST_REMOTE_MCP_* secrets/var (kept separate from MDB_MCP_API_* so cloud-dev
  creds don't leak into other tests). Until the secrets exist, e2e self-skips.
- scripts/path-b-smoke-test.sh: one-time provisioning of the ingress credentials
  via the group-level mcpConfig flow.
- Document e2e testing, provisioning, and secret rotation in CONTRIBUTING.md.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant