Skip to content

test: cover MCP server tools - #76

Merged
Emmy123222 merged 1 commit into
Emmy123222:mainfrom
Heazzy500:fix/issue-28
Sep 3, 2026
Merged

test: cover MCP server tools#76
Emmy123222 merged 1 commit into
Emmy123222:mainfrom
Heazzy500:fix/issue-28

Conversation

@Heazzy500

Copy link
Copy Markdown

Summary

  • extract the web_search, ai_summarize, and check_balance handlers into testable functions
  • wire the MCP server to use those handlers
  • add Vitest coverage for successful responses and error paths, including Horizon 404 and Groq failures

Verification

  • vitest run (4 tests passed)
  • TypeScript node config check passed

Closes #28

@vercel

vercel Bot commented Aug 26, 2026

Copy link
Copy Markdown

@zeemscript is attempting to deploy a commit to the Emmanuel's projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Aug 26, 2026

Copy link
Copy Markdown

@Heazzy500 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@Heazzy500

Copy link
Copy Markdown
Author

@Emmy123222 The merge conflicts for this PR have been resolved against the latest main and pushed to Heazzy500:fix/issue-28. Please re-run/inspect CI when available.

@AbuJulaybeeb

Copy link
Copy Markdown
Collaborator

@Emmy123222 The merge conflicts for this PR have been resolved against the latest main and pushed to Heazzy500:fix/issue-28. Please re-run/inspect CI when available.

nope.
pull form main, rebase and push

@Heazzy500

Copy link
Copy Markdown
Author

@Emmy123222 @Heazzy500 Rebased safely onto current upstream main and pushed the resolved branch. New verified head: 653a07a. The PR references Fixes #28. Verification: dependency manifest conflicts resolved using upstream’s current lockfile/tool versions while preserving the MCP test files; git diff --check passed. Please rerun/inspect CI.

@AbuJulaybeeb

Copy link
Copy Markdown
Collaborator

@Emmy123222 @Heazzy500 Rebased safely onto current upstream main and pushed the resolved branch. New verified head: 653a07a. The PR references Fixes #28. Verification: dependency manifest conflicts resolved using upstream’s current lockfile/tool versions while preserving the MCP test files; git diff --check passed. Please rerun/inspect CI.

The branch still cannot be rebased due to conflicts.

@Heazzy500

Copy link
Copy Markdown
Author

@Emmy123222 Merge conflicts resolved for this PR against latest main. Rebased fix/issue-28 onto upstream/main and pushed — new head: 1eb2c61. Conflict files: mcp-server/index.ts, package.json, package-lock.json. Validation: git diff --check clean; working tree clean; reviewed merged MCP test coverage (handlers.ts, handlers.test.ts, vitest.config.ts) — no node_modules present so ran light validation (no test run). Please review / re-run CI when convenient. Thanks!

@Heazzy500

Copy link
Copy Markdown
Author

@Emmy123222 @Heazzy500 PR #76 was rebased onto the current upstream main and the duplicate package-sync commits were removed; the focused MCP implementation/test changes remain in commit db59d06. The branch has been force-updated and is ready for CI/review.

@Emmy123222
Emmy123222 merged commit a4a3d86 into Emmy123222:main Sep 3, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add test coverage for MCP server tools

4 participants