[test] Add tests for mcp.callSDKMethodWithReconnect and reconnectSDKTransport

[github-actions]

Test Coverage Improvement: mcp reconnect SDK functions

Function Analyzed

• Package: internal/mcp
• Functions: reconnectSDKTransport, callSDKMethodWithReconnect, listResources, listPrompts, readResource, getPrompt, ServerInfo
• Previous Coverage: reconnectSDKTransport 0%, callSDKMethodWithReconnect 33.3%, package overall 84.5%
• New Coverage: reconnectSDKTransport 100%, callSDKMethodWithReconnect 100%, package overall 92.2%
• Complexity: High

Why These Functions?

reconnectSDKTransport and callSDKMethodWithReconnect implement the session reconnect state machine — the most complex, branchy logic in internal/mcp — yet had 0% and 33.3% coverage respectively. listResources, listPrompts, and related methods had only their error path covered (28.6%), missing the happy path through a real SDK session entirely.

Tests Added

• ✅ reconnectSDKTransport — unsupported transport type (default branch)
• ✅ reconnectSDKTransport — Streamable connect failure (bad URL)
• ✅ reconnectSDKTransport — SSE connect failure
• ✅ reconnectSDKTransport — existing session closed before reconnect
• ✅ callSDKMethodWithReconnect — happy path (no error)
• ✅ callSDKMethodWithReconnect — non-session-not-found error (no reconnect triggered)
• ✅ callSDKMethodWithReconnect — session-not-found + reconnect fails
• ✅ callSDKMethodWithReconnect — session-not-found + reconnect succeeds + retry succeeds
• ✅ listResources — with real streamable session, empty result
• ✅ listPrompts — with real streamable session, empty result
• ✅ readResource — with real streamable session (error from server expected)
• ✅ getPrompt — with real streamable session (error from server expected)
• ✅ ServerInfo — with and without session
• ✅ NewHTTPConnection — server info population from initialize response

Coverage Report

Before: reconnectSDKTransport 0.0%, callSDKMethodWithReconnect 33.3%, package 84.5%
After:  reconnectSDKTransport 100%, callSDKMethodWithReconnect 100%, package 92.2%
Improvement: +7.7% overall package

Test Execution

All 18 tests pass:

--- PASS: TestReconnectSDKTransport_UnsupportedType (0.00s)
--- PASS: TestReconnectSDKTransport_EmptyType (0.00s)
--- PASS: TestReconnectSDKTransport_StreamableConnectFailure (0.00s)
--- PASS: TestReconnectSDKTransport_SSEConnectFailure (0.00s)
--- PASS: TestReconnectSDKTransport_ExistingSessionClosed (0.00s)
--- PASS: TestCallSDKMethodWithReconnect_NoError (0.00s)
--- PASS: TestCallSDKMethodWithReconnect_NonSessionError (0.00s)
--- PASS: TestCallSDKMethodWithReconnect_SessionNotFoundReconnectFails (0.00s)
--- PASS: TestCallSDKMethodWithReconnect_SessionNotFoundReconnectSucceeds (0.00s)
--- PASS: TestListResources_WithSession (0.00s)
--- PASS: TestListResources_Empty (0.00s)
--- PASS: TestListPrompts_WithSession (0.00s)
--- PASS: TestListPrompts_Empty (0.00s)
--- PASS: TestReadResource_WithSession (0.00s)
--- PASS: TestGetPrompt_WithSession (0.00s)
--- PASS: TestServerInfo_WithSession (0.00s)
--- PASS: TestServerInfo_WithoutSession (0.00s)
--- PASS: TestNewHTTPConnection_ServerInfoPopulated (0.00s)
PASS

---

Generated by Test Coverage Improver
Next run will target the next most complex under-tested function

Warning

Firewall blocked 8 domains

The following domains were blocked by the firewall during workflow execution:

• 172.30.0.50
• go.opentelemetry.io
• go.yaml.in
• golang.org
• google.golang.org
• gopkg.in
• proxy.golang.org
• releaseassets.githubusercontent.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "172.30.0.50"
    - "go.opentelemetry.io"
    - "go.yaml.in"
    - "golang.org"
    - "google.golang.org"
    - "gopkg.in"
    - "proxy.golang.org"
    - "releaseassets.githubusercontent.com"

See Network Configuration for more information.

Generated by Test Coverage Improver · sonnet46 15M · ◷