add configuration options

Author: devalog

fern/products/sdks/guides/testing.mdx

@@ -9,18 +9,23 @@ Fern provides comprehensive testing for your SDKs through generated and handwrit
 
 <Markdown src="/snippets/pro-plan.mdx"/>
 
-Fern auto-generates tests that must pass before SDK release. Fern generates a GitHub workflow in each SDK repository that runs unit and mock server tests on every pull request, commit, and release.
-
+Fern auto-generates tests that must pass before SDK release. Fern generates a GitHub workflow in each SDK repository that runs unit tests and any enabled mock server tests on every pull request, commit, and release.
 
 ### Unit tests
 
 Fern generates unit tests for all SDK languages. They verify individual methods in isolation without making network calls.
 
 ### Mock server tests
 
-Mock server (wire) tests run your SDK against a mock server generated from your API definition. They validate serialization, endpoints, headers, and status code handling. 
+Mock server (wire) tests run your SDK against a mock server generated from your API definition. They verify that the SDK sends and receives HTTP requests as expected. These tests are generated for all endpoints in a service.
+
+Mock server tests are available for TypeScript, Go, and Java. Configure mock server tests in your `generators.yml`:
 
-Mock server tests are available for TypeScript, Go, and Java. 
+| Language | Configuration | Default |
+|----------|---------------|---------|
+| TypeScript | [`generateWireTests`](/sdks/generators/typescript/configuration#generatewiretests) | true |
+| Go | [`enableWireTests`](/sdks/generators/go/configuration#enablewiretests) | false |
+| Java | [`enable-wire-tests`](/sdks/generators/java/configuration#enablewiretests) | false |
 
 ## Integration tests
 

fern/products/sdks/overview/go/configuration.mdx

@@ -36,6 +36,10 @@ Specifies the name of the generated client struct. This determines the primary c
 Sets the name of the exported client that will be used in code snippets and documentation examples. This is useful for customizing how the client appears in generated documentation.
 </ParamField>
 
+<ParamField path="enableWireTests" type="string" default="false" required={false} toc={true}>
+When enabled, generates [mock server (wire) tests](/sdks/deep-dives/testing#mock-server-tests) to verify that the SDK sends and receives HTTP requests as expected.
+</ParamField>
+
 <ParamField path="importPath" type="string" required={false} toc={true}>
 Use this option if you plan to depend on the generated Go SDK from within your project, and **not** depend on it as a separate, published Go module.
 

fern/products/sdks/overview/java/configuration.mdx

@@ -66,6 +66,10 @@ When enabled, generates inline types for nested schemas instead of creating sepa
 When enabled, generates public constructors for model types.
 </ParamField>
 
+<ParamField path="enable-wire-tests" type="boolean" default="false" required={false} toc={true}>
+When enabled, generates [mock server (wire) tests](/sdks/deep-dives/testing#mock-server-tests) to verify that the SDK sends and receives HTTP requests as expected.
+</ParamField>
+
 <ParamField path="generate-unknown-as-json-node" type="boolean" default="false" required={false} toc={true}>
 When enabled, generates unknown or untyped properties as structured JSON objects instead of raw Object types. This provides better type safety and easier manipulation of dynamic JSON content while maintaining flexibility for unknown data structures.
 </ParamField>

fern/products/sdks/overview/typescript/configuration.mdx

@@ -172,6 +172,10 @@ Choose whether you want to support Node.js 16 and above (`Node16`), or Node.js 1
 *    `Node18` uses the native FormData API, and accepts a wider range of types for file uploads, such as `Buffer`, `File`, `Blob`, `Readable`, `ReadableStream`, `ArrayBuffer`, and `Uint8Array`
 </ParamField>
 
+<ParamField path="generateWireTests" type="boolean" default="true" toc={true}>
+Generates [mock server (wire) tests](/sdks/deep-dives/testing#mock-server-tests) to verify that the SDK sends and receives HTTP requests as expected.
+</ParamField>
+
 <ParamField path="includeContentHeadersOnFileDownloadResponse" type="boolean" toc={true}>
 
 Includes the content type and content length from binary responses. The user will receive an object of the following type: