如何为含私有HttpClient方法的ASP.NET Core类编写Xunit单元测试

直接Mock私有方法不是推荐做法，这类测试会和类的内部实现强耦合，后续维护成本高。更合理的方案是重构代码，将HTTP请求逻辑提取为独立接口，通过依赖注入解耦，这样就能轻松Mock响应。

步骤1：提取HTTP请求逻辑到接口和实现类 #

把原私有方法MySendAsync的逻辑移到独立的接口和实现类中，让MyPlatform通过依赖注入使用这个接口：

// 定义HTTP发送接口
public interface IHttpSender
{
    Task<HttpResponseMessage> SendAsync(string method, string uri, string jsonContent, string apiKey, string headerToken = null);
}

// 接口实现类，复用原私有方法的逻辑
public class HttpSender : IHttpSender
{
    public async Task<HttpResponseMessage> SendAsync(string method, string uri, string jsonContent, string apiKey, string headerToken = null)
    {
        try
        {
            using (HttpClientHandler httpHandler = new())
            {
                var request = new HttpRequestMessage(new HttpMethod(method), uri)
                {
                    Content = new NoEncodingJsonContent(jsonContent)
                };

                request.Headers.Add("API-KEY", apiKey);

                if (headerToken != null)
                {
                    request.Headers.Add("Token", headerToken);
                }

                httpHandler.ServerCertificateCustomValidationCallback = (sender, cert, chain, sslPolicyErrors) => true;

                using HttpClient client = new(httpHandler);
                client.Timeout = TimeSpan.FromSeconds(10);

                return await client.SendAsync(request);
            }
        }
        catch (Exception ex)
        {
            throw new Exception(ex.Message);
        }
    }
}

步骤2：修改MyPlatform类，注入IHttpSender #

调整MyPlatform的构造函数，注入IHttpSender实例，替换原私有方法调用：

public class MyPlatform : BasePlatform, IPlatformAction
{
    private readonly string _apiKey;
    private readonly IHttpSender _httpSender;

    // 构造函数注入IHttpSender，测试时可传入Mock实例
    public MyPlatform(IHttpSender httpSender)
    {
        _apiKey = <MyAPI-Key>;
        _httpSender = httpSender;
    }

    public async Task<Token> Authorize(LoginDTO login)
    {
        using HttpResponseMessage response = await _httpSender.SendAsync(
            "POST", 
            "URI/Authenticate", 
            JsonSerializer.Serialize(login), 
            _apiKey);
            
        string jsonContent = await response.Content.ReadAsStringAsync();

        if (response.IsSuccessStatusCode)
        {
            AuthResponseDto results = JsonSerializer.Deserialize<AuthResponseDto>(jsonContent, _jsonOptions);
            return new Token { AccessToken = results.Token };
        }

        // 补充原代码缺失的失败分支处理
        throw new InvalidOperationException("授权请求失败");
    }
}

步骤3：编写Xunit测试用例（使用Moq） #

现在可以轻松MockIHttpSender来模拟不同的HTTP响应：

public class MyPlatformTests
{
    [Fact]
    public async Task Authorize_ValidCredentials_ReturnsToken()
    {
        // 准备Mock数据
        var mockHttpSender = new Mock<IHttpSender>();
        var fakeToken = "fake-auth-token-789";
        var fakeResponseContent = JsonSerializer.Serialize(new AuthResponseDto { Token = fakeToken });
        var successResponse = new HttpResponseMessage(HttpStatusCode.OK)
        {
            Content = new StringContent(fakeResponseContent, Encoding.UTF8, "application/json")
        };

        // 配置Mock行为
        mockHttpSender.Setup(s => s.SendAsync(
            "POST",
            "URI/Authenticate",
            It.IsAny<string>(),
            It.IsAny<string>(),
            null))
        .ReturnsAsync(successResponse);

        // 初始化测试对象
        var platform = new MyPlatform(mockHttpSender.Object);
        var testLogin = new LoginDTO { Username = "test", Password = "test123" };

        // 执行测试
        var result = await platform.Authorize(testLogin);

        // 验证结果
        Assert.NotNull(result);
        Assert.Equal(fakeToken, result.AccessToken);
        mockHttpSender.Verify(s => s.SendAsync(
            "POST",
            "URI/Authenticate",
            It.IsAny<string>(),
            It.IsAny<string>(),
            null), Times.Once);
    }

    [Fact]
    public async Task Authorize_InvalidCredentials_ThrowsException()
    {
        // 准备Mock数据
        var mockHttpSender = new Mock<IHttpSender>();
        var failureResponse = new HttpResponseMessage(HttpStatusCode.Unauthorized);

        // 配置Mock行为
        mockHttpSender.Setup(s => s.SendAsync(
            "POST",
            "URI/Authenticate",
            It.IsAny<string>(),
            It.IsAny<string>(),
            null))
        .ReturnsAsync(failureResponse);

        // 初始化测试对象
        var platform = new MyPlatform(mockHttpSender.Object);
        var testLogin = new LoginDTO { Username = "wrong", Password = "wrong123" };

        // 验证异常抛出
        await Assert.ThrowsAsync<InvalidOperationException>(() => platform.Authorize(testLogin));
    }
}

为什么不推荐Mock私有方法？ #

如果非要Mock私有方法，需要依赖反射或第三方工具（如Microsoft Fakes），但这种方式存在以下问题：

• 测试与类的内部实现强耦合，私有方法签名、逻辑变更都会导致测试失败
• 代码可读性差，维护成本高
• 违背了面向接口编程的设计原则

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