-
Notifications
You must be signed in to change notification settings - Fork 146
Add integration tests for vMCP server #2624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2624 +/- ##
==========================================
- Coverage 55.47% 55.03% -0.45%
==========================================
Files 312 315 +3
Lines 29714 29952 +238
==========================================
Hits 16485 16485
- Misses 11789 12027 +238
Partials 1440 1440 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
ac0d8f3 to
c6612a8
Compare
yrobla
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how are those tests run?
|
LGTM, Yolanda has some comments. |
it's just part of |
The tests use real MCP backend servers created with mark3labs/mcp-go SDK to ensure authentic protocol behavior. Test helpers in test/integration/vmcp/helpers/ provide reusable utilities for creating vMCP servers, MCP clients, backend servers, and common test assertions.
Use select statement instead of ctx.Err() check to avoid race condition when checking for context cancellation in the goroutine error handler. This follows Go best practices for context handling. Addresses review comment from @yrobla.
411ccbe to
f3ad1ac
Compare
The tests use real MCP backend servers created with mark3labs/mcp-go SDK to ensure authentic protocol behavior.
Test helpers in test/integration/vmcp/helpers/ provide reusable utilities for creating vMCP servers, MCP clients, backend servers, and common test assertions.