Update tapir-apispec-docs, tapir-core, ... to 1.11.37 #25
GitHub Actions / Test report for -java-11
succeeded
Jul 18, 2025 in 1s
25 passed, 0 failed and 0 skipped
| Report | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| core/target/test-reports/TEST-chimp.McpHandlerSpec.xml | 16✅ | 101ms | ||
| core/target/test-reports/TEST-chimp.protocol.ModelSpec.xml | 9✅ | 269ms |
✅ core/target/test-reports/TEST-chimp.McpHandlerSpec.xml
16 tests were completed in 101ms with 16 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| chimp.McpHandlerSpec | 16✅ | 101ms |
✅ chimp.McpHandlerSpec
✅ McpHandler should respond to initialize
✅ McpHandler should list available tools
✅ McpHandler should call a tool successfully (echo)
✅ McpHandler should call a tool successfully (add)
✅ McpHandler should accept notifications
✅ McpHandler should return an error for unknown tool
✅ McpHandler should return an error for invalid arguments
✅ McpHandler should return an error for missing arguments
✅ McpHandler should return an error for missing tool name
✅ McpHandler should return an error for tool logic failure
✅ McpHandler should return an error for unknown method
✅ McpHandler should handle batch requests with mixed results
✅ McpHandler should call a tool with a header and receive the header's value in the response
✅ McpHandler should call a tool with a header and receive multiple header's values in the response
✅ McpHandler should call a tool without a header value and receive 'no header' in the response
✅ McpHandler should handle batch requests with mixed headers
✅ core/target/test-reports/TEST-chimp.protocol.ModelSpec.xml
9 tests were completed in 269ms with 9 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| chimp.protocol.ModelSpec | 9✅ | 269ms |
✅ chimp.protocol.ModelSpec
✅ JSONRPCMessage should handle Request messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle Notification messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle Response messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle Error messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle BatchRequest messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle BatchResponse messages according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle both numeric and string request IDs according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle optional parameters according to JSON-RPC 2.0 spec
✅ JSONRPCMessage should handle all standard JSON-RPC error codes according to spec
Loading