Use MockWebServer the same way that you use mocking frameworks like
[Mockito](https://github.com/mockito/mockito):

1. Script the mocks.
2. Run application code.
3. Verify that the expected requests were made.

Here's a complete example:

### Java
```java
public void test() throws Exception {
  // Create a MockWebServer. These are lean enough that you can create a new
  // instance for every unit test.

    }

    @Test
    void testCompleteWireFormatRoundTrip() {
        trans2QueryPathInfo = new Trans2QueryPathInformation(config, TEST_FILENAME, TEST_INFO_LEVEL);

        // Test complete wire format writing
        byte[] setupBuffer = new byte[256];
        byte[] paramBuffer = new byte[512];
        byte[] dataBuffer = new byte[256];

     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Waiting for application startup.
     <span style="background-color:#007166"><font color="#D3D7CF"> INFO </font></span>  Application startup complete.
```

</div>

/// tip | 提示

在生产环境中，你会使用 `fastapi run` 而不是 `fastapi dev`。🚀

///

在内部，**FastAPI CLI** 使用 [Uvicorn](https://www.uvicorn.dev)，这是一个高性能、适用于生产环境的 ASGI 服务器。😎

        ) {
          result.flush()
          handleSocketEffect(socketEffect, socket, stream)
        }
    }

    return result
  }

  /** Returns true if processing this exchange is complete. */
  private fun handleSocketEffect(
    effect: SocketEffect?,
    socket: MockWebServerSocket,
    stream: Http2Stream? = null,
  ): Boolean {
    if (effect == null) return false

    when (effect) {

                return true;
            });
            resultBuf.append("Exported ").append(count).append(" documents.");
            if (logger.isInfoEnabled()) {
                logger.info("[EXPORT] Completed: exportedCount={}, elapsedTime={}ms", count, System.currentTimeMillis() - startTime);
            }
        } catch (final Exception e) {
            logger.warn("Failed to export documents.", e);

You can define background tasks to be run *after* returning a response.

This is useful for operations that need to happen after a request, but that the client doesn't really have to be waiting for the operation to complete before receiving the response.

This includes, for example:

* Email notifications sent after performing an action:

            Thread.sleep(100);
        } catch (Exception e) {
            // May throw due to null user when task executes, which is expected
        }

        assertTrue("scheduleParentGroupLookup should complete without immediate error", true);
    }

    /**
     * Test that empty groupIds list does not schedule any task.
     */
    @Test

        }
    }

    @Nested
    @DisplayName("Integration Scenarios")
    class IntegrationTests {

        @Test
        @DisplayName("Should complete full connection lifecycle")
        void testFullConnectionLifecycle() throws Exception {
            // Given
            when(transportPool.getSmbTransport(context, TEST_HOST, DEFAULT_PORT, false, false)).thenReturn(transport);

	ri := &batchJobInfo{
		JobID:     job.ID,
		JobType:   string(job.Type()),
		StartTime: job.Started,
	}
	if err := ri.loadOrInit(ctx, api, job); err != nil {
		return err
	}
	if ri.Complete {
		return nil
	}

	globalBatchJobsMetrics.save(job.ID, ri)
	lastObject := ri.Object

	retryAttempts := job.KeyRotate.Flags.Retry.Attempts
	if retryAttempts <= 0 {

 * <p>
 * To fully understand the information exposed by this class a description
 * of the access check algorithm used by Windows is required. The following
 * is a basic description of the algorithm. For a more complete description
 * we recommend reading the section on Access Control in Keith Brown's
 * "The .NET Developer's Guide to Windows Security" (which is also
 * available online).
 * <p>