Update the tests README for Ruby server coverage
The README still said the Ruby weather server was uncovered and described the resultType gap as unfixable from an example. Both stopped being true when the server test landed. Also move the no-API-key comment below the Ruby server test. It describes the client tests, and sat where it read as describing the server one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
d9005ebe03
commit
cfda589119
1 changed files with 5 additions and 7 deletions
|
|
@ -84,10 +84,6 @@ test_weather_server_go() {
|
|||
node "${TEST_CLIENT}" "${server_bin}"
|
||||
}
|
||||
|
||||
# The client tests drive the no-API-key path, where each client prints a notice
|
||||
# and exits. Empty rather than unset: dotenv skips a name already present in
|
||||
# ENV, so a key in the environment or a local .env would start the chat loop.
|
||||
|
||||
# Test: Ruby weather server
|
||||
test_weather_server_ruby() {
|
||||
check_dependency ruby || return 1
|
||||
|
|
@ -97,6 +93,10 @@ test_weather_server_ruby() {
|
|||
(cd "${server_dir}" && node "${TEST_CLIENT}" bundle exec ruby weather.rb)
|
||||
}
|
||||
|
||||
# The client tests drive the no-API-key path, where each client prints a notice
|
||||
# and exits. Empty rather than unset: dotenv skips a name already present in
|
||||
# ENV, so a key in the environment or a local .env would start the chat loop.
|
||||
|
||||
# Test: Python MCP client
|
||||
test_mcp_client_python() {
|
||||
check_dependency uv || return 1
|
||||
|
|
|
|||
Loading…
Reference in a new issue