Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds an initial automated smoke test setup for
reactome-mcp.The main thing I wanted to do here was add a lightweight way to catch breakage in the MCP surface without relying on manual Inspector testing or live Reactome service calls every time. To make that possible, I pulled server construction into a small shared factory that can be used both by the runtime entrypoint and by tests.
Included in this PR
src/server.tsso the MCP server can be created in tests without starting stdiosrc/index.tsto use the shared server construction pathbuild:test/testscriptsdist-test/node:testCurrent test coverage
The suite currently checks:
server initialization
representative tool/resource/template registration
mocked smoke tests for:
reactome_searchreactome_get_pathwayreactome_get_analysis_resultinvalid blank query/token cases
representative static and templated resource handling
Notes
The tests stub the content and analysis client boundaries so they stay fast and deterministic.
I also tightened validation a bit for blank search queries and analysis tokens, mainly so those failure cases are clearer and easier to cover in tests.
Verified
npm run buildnpm test