From 65260c91d5112fa8a85e1c36596057e183c42d94 Mon Sep 17 00:00:00 2001 From: Jeremiah Lowin <153965+jlowin@users.noreply.github.com> Date: Fri, 24 Oct 2025 18:40:30 -0400 Subject: [PATCH] Add version badge for run_server_async in tests docs (#2237) Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Jeremiah Lowin --- docs/development/tests.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/development/tests.mdx b/docs/development/tests.mdx index d317bb6dc..3bbf64ce2 100644 --- a/docs/development/tests.mdx +++ b/docs/development/tests.mdx @@ -4,6 +4,8 @@ description: "Testing patterns and requirements for FastMCP" icon: vial --- +import { VersionBadge } from "/snippets/version-badge.mdx" + Good tests are the foundation of reliable software. In FastMCP, we treat tests as first-class documentation that demonstrates how features work while protecting against regressions. Every new capability needs comprehensive tests that demonstrate correctness. ## FastMCP Tests @@ -301,6 +303,8 @@ While in-memory testing covers most unit testing needs, you'll occasionally need #### In-Process Network Testing (Preferred) + + For most network transport tests, use `run_server_async` with AnyIO task groups. This runs the server as a task in the same process, providing fast, deterministic tests with full debugger support: ```python