testing
Testing
The rules are in AGENTS.md under Always test new
or modified code: new behavior comes with tests, every TypeScript file clears
the per-file coverage gate, test at the protocol level where you can, and keep
expected error output off the console. This skill explains the harness each
server has, how to write a test with it, which command runs what, and how to
clear the per-file coverage gate.
Driving a running server by hand, with the Inspector or an LLM client, is
/client-smoke. It is evidence for a PR, not a substitute for a test.
Every server is tested in-process, and every file is gated. The four
TypeScript servers link a real Client to the server over an in-memory
transport (#4854); the three Python servers link a ClientSession to the real
serve() over in-memory streams (#4855). Both languages hold each file to a
per-file coverage floor, in CI and in npm run local:gate.