test(mcp-integrations): add MCP plugin and backend integration tests#3232
Open
HusneShabbir wants to merge 2 commits into
Open
test(mcp-integrations): add MCP plugin and backend integration tests#3232HusneShabbir wants to merge 2 commits into
HusneShabbir wants to merge 2 commits into
Conversation
HusneShabbir
requested review from
a team,
gabemontero,
johnmcollier and
thepetk
as code owners
Missing ChangesetsThe following package(s) are changed by this PR but do not have a changeset:
See CONTRIBUTING.md for more information about how to add changesets. Changed Packages
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3232 +/- ##
==========================================
+ Coverage 60.97% 61.00% +0.03%
==========================================
Files 2098 2098
Lines 65140 65150 +10
Branches 17029 17029
==========================================
+ Hits 39721 39747 +26
+ Misses 25180 25164 -16
Partials 239 239
*This pull request uses carry forward flags. Click here to find out more. Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
HusneShabbir
force-pushed
the
test/mcp-integrations-integration-tests
branch
2 times, most recently
from
4921c97 to
f1a9e17
Compare
Add integration tests for action registration and MCP tools/list/call coverage, including auth and pluginSources filtering. Mark read-only actions with MCP attributes and configure backend test runner to exit cleanly after integration runs. Co-authored-by: Cursor <cursoragent@cursor.com>
HusneShabbir
force-pushed
the
test/mcp-integrations-integration-tests
branch
from
f1a9e17 to
827b7fe
Compare
johnmcollier
requested changes
May 26, 2026
Remove MCP readOnly attributes on actions not covered by hint assertions. Consolidate backend integration tests, tighten 401 auth checks, and add test:unit/test:integration scripts with --watch=false for clean local exits. Co-authored-by: Cursor <cursoragent@cursor.com>
|
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
2 participants
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
Adds integration tests for MCP overlay plugins: lightweight plugin wiring checks (action registration) and a backend HTTP suite against
/api/mcp-actions/v1(tools/list,tools/call, auth).Also adds
test:unit/test:integrationscripts (--watch=falseso local runs exit instead of staying in Backstage’s default Jest watch mode) and backend test dependencies for the MCP client.Test file structure
Total: 4 files · 11 integration tests (included in CI via
yarn test:all)Plugin tests — “does the plugin register the right actions?”
Each file starts
startTestBackend, capturesactionsRegistry.register(), and asserts action names and count.software-catalog-mcp-extras/.../plugin.integration.test.tsquery-catalog-entities(1)techdocs-mcp-extras/.../plugin.integration.test.tsfetch-techdocs,analyze-techdocs-coverage,retrieve-techdocs-content(3)scaffolder-mcp-extras/.../plugin.integration.test.tsexecute-template,fetch-template-metadata,get-scaffolder-task-logs,list-scaffolder-actions,list-scaffolder-tasks,validate-scaffolder(6)Backend test — “does the MCP server work over HTTP?”
packages/backend/src/mcp-tools.integration.test.ts— Streamable HTTP MCP client against a real test backend (shared backend for fullpluginSources; MCP session teardown viaterminateSession+client.close).inputSchema, read-only/destructive MCP hints (actions that declareattributesonly)query-catalog-entities→{ entities: [] }analyze-techdocs-coverage→ zero coverage statsfetch-template-metadata→{ templates: [] }query-catalog-entitiestool401with expected error messagetools/listsucceedsSupporting changes
attributesonfetch-techdocsandretrieve-techdocs-content(read-only MCP hints covered by the backend test; scaffolder read-only/destructive tools already hadattributesonmain)devDependencies:@backstage/backend-test-utils,@modelcontextprotocol/sdk,@backstage/backend-plugin-api,@backstage/errors,@backstage/plugin-catalog-nodetest:unit/test:integration; backendtest:integrationfor the HTTP suite;--watch=falseon integration scripts so they exit locally (CI already setsCI=true)CI
When
workspaces/mcp-integrationschanges, Test changed packages runsyarn test:all, which includes these integration tests alongside existing unit tests (no separate job required).