test: Add unit test for projects/app/src/service/support/mcp/utils.ts #5430
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.
Trigger Info
Summary
This PR introduces the following changes:
Dependency Updates:
Updated
@fastgpt-sdk/plugin
from0.1.7
to0.1.8
.Added
@babel/[email protected]
as a dependency in thenext-i18next
package configuration.Testing Enhancements:
Added a new test file
utils.test.ts
undertest/cases/service/support/mcp/
to cover utility functions in the MCP service.Implemented unit tests for the following utility functions:
pluginNodes2InputSchema
: Converts plugin nodes to input schema.workflow2InputSchema
: Creates input schema for workflows.getMcpServerTools
: Retrieves MCP server tools based on the provided key.callMcpServerTool
: Executes an MCP server tool and validates the response.Mocking Improvements:
Mocked various modules and functions to isolate and test the utility functions effectively, including:
MongoMcpKey
MongoApp
authAppByTmbId
getAppLatestVersion
getUserChatInfoAndAuthTeamPoints
dispatchWorkFlow
saveChat
createChatUsage
These changes enhance the robustness of the MCP service utilities and ensure better test coverage for critical functionalities.
Coverage
The change in coverage value, such as:
0% -> 50%
, indicates that the coverage was 0% before writing the tests and 50% after writing them.https://web.dev/articles/ta-code-coverage
Test Statuses
Tip
You can
@gru-agent
and leave your feedback. TestGru will make adjustments based on your inputTip
You can
@gru-agent rebase
to rebase the PR.Tip
You can
@gru-agent redo
to reset or rebase before redoing the PR.Tip
To modify the test code yourself, click here Edit Test Code