Extract MCP::Tool::Annotations unit tests
#117
Merged
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
The tests related to `MCP::Tool::Annotations` will be extracted from the `MCP::ToolTest` test class into a dedicated `MCP::Tool::AnnotationsTest` unit test class as a testing pair. This improves test clarity, file level test independence, and file level execution speed. It also ensures consistent placement as a testing pair under `MCP::Tool::*`: ```console $ ls lib/mcp/tool/ annotations.rb input_schema.rb response.rb $ ls test/mcp/tool/ annotations_test.rb input_schema_test.rb response_test.rb ```
atesgoral
approved these changes
Aug 27, 2025
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.
Motivation and Context
The tests related to
MCP::Tool::Annotationswill be extracted from theMCP::ToolTesttest class into a dedicatedMCP::Tool::AnnotationsTestunit test class as a testing pair.This improves test clarity, file level test independence, and file level execution speed. It also ensures consistent placement as a testing pair under
MCP::Tool::*:How Has This Been Tested?
The same number of tests as before are being executed.
Breaking Changes
None.
Types of changes
Checklist