如何在Moq中为HttpClient实现带断言的多请求序列Mock？

完全可以实现。针对你遇到的多请求序列问题，下面提供两种实用方案：

方案一：借助Moq的回调+捕获请求参数 #

虽然HttpMessageHandler的SendAsync是受保护方法，但Moq可以通过Protected() API设置它的行为，同时用回调捕获请求参数，后续做验证，还能根据参数动态返回响应。

代码示例： #

// 用来捕获所有请求的列表，后续验证用
var capturedRequests = new List<HttpRequestMessage>();

// 初始化Mock<HttpMessageHandler>
var mockHandler = new Mock<HttpMessageHandler>();

// 设置SendAsync的行为：捕获请求，根据参数返回对应响应
mockHandler.Protected()
    .Setup<Task<HttpResponseMessage>>(
        "SendAsync",
        ItExpr.IsAny<HttpRequestMessage>(),
        ItExpr.IsAny<CancellationToken>()
    )
    .Callback<HttpRequestMessage, CancellationToken>((req, token) =>
    {
        // 捕获请求，后续统一验证参数
        capturedRequests.Add(req);
        // 也可在此直接做参数断言，多请求场景下不会阻塞响应返回
        Assert.Equal(HttpMethod.Get, req.Method);
        Assert.StartsWith("https://api.example.com/", req.RequestUri.ToString());
    })
    .ReturnsAsync((HttpRequestMessage req, CancellationToken token) =>
    {
        // 根据请求参数动态返回响应
        if (req.RequestUri.PathAndQuery.Contains("/users"))
        {
            return new HttpResponseMessage(HttpStatusCode.OK)
            {
                Content = new StringContent(@"{""id"":1,""name"":""Test""}")
            };
        }
        else if (req.RequestUri.PathAndQuery.Contains("/posts"))
        {
            return new HttpResponseMessage(HttpStatusCode.OK)
            {
                Content = new StringContent(@"[{""id"":1,""title"":""Post 1""}]")
            };
        }
        return new HttpResponseMessage(HttpStatusCode.NotFound);
    });

// 创建HttpClient并传入Mock的Handler
var httpClient = new HttpClient(mockHandler.Object);

// 执行多请求逻辑
await httpClient.GetAsync("https://api.example.com/users");
await httpClient.GetAsync("https://api.example.com/posts");

// 最后验证捕获的请求参数
Assert.Equal(2, capturedRequests.Count);
Assert.Equal("/users", capturedRequests[0].RequestUri.PathAndQuery);
Assert.Equal("/posts", capturedRequests[1].RequestUri.PathAndQuery);

方案二：自定义HttpMessageHandler子类 #

如果觉得Moq的Protected API不够直观，可以自己写一个继承自HttpMessageHandler的类，重写SendAsync方法，完全掌控请求处理逻辑，包括参数验证和动态响应。

代码示例： #

public class MockableHttpMessageHandler : HttpMessageHandler
{
    // 捕获请求的列表
    public List<HttpRequestMessage> CapturedRequests { get; } = new List<HttpRequestMessage>();
    // 自定义响应逻辑，可设置为Func或预设的响应映射
    public Func<HttpRequestMessage, CancellationToken, Task<HttpResponseMessage>> ResponseFactory { get; set; }

    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        CapturedRequests.Add(request);
        // 直接在处理逻辑里做参数验证
        if (request.Method != HttpMethod.Get)
        {
            throw new ArgumentException("只允许GET请求");
        }
        // 调用自定义响应工厂返回动态响应
        return await ResponseFactory(request, cancellationToken);
    }
}

// 使用示例
var mockHandler = new MockableHttpMessageHandler();
// 设置动态响应逻辑
mockHandler.ResponseFactory = async (req, token) =>
{
    if (req.RequestUri.PathAndQuery.Contains("/users"))
    {
        return new HttpResponseMessage(HttpStatusCode.OK)
        {
            Content = new StringContent(@"{""id"":1,""name"":""Test""}")
        };
    }
    return new HttpResponseMessage(HttpStatusCode.NotFound);
};

var httpClient = new HttpClient(mockHandler);

// 执行请求
await httpClient.GetAsync("https://api.example.com/users");

// 验证请求参数
Assert.Equal(1, mockHandler.CapturedRequests.Count);
Assert.Equal(HttpMethod.Get, mockHandler.CapturedRequests[0].Method);

关键说明： #

• 多请求场景下，不要在Moq的Setup里直接用Assert（会导致第一次断言失败后后续请求无法处理），而是把断言放在回调里，或者最后统一验证捕获的请求列表。
• 自定义Handler的方式更灵活，适合复杂的多请求序列场景，比如需要按顺序返回不同响应，或者需要严格验证每个请求的参数。

内容的提问来源于stack exchange，提问作者jokarl