模拟HttpContext时SignOutAsync调用失败的问题排查

问题原因 #

SignOutAsync扩展方法内部会通过HttpContext.RequestServices获取IServiceProvider，再用它获取IAuthenticationService实例。你用Moq创建的HttpContext默认未配置RequestServices，导致调用时抛出ArgumentNullException。

解决方案 #

方案1：给Moq的HttpContext配置RequestServices

直接为模拟的HttpContext设置有效的IServiceProvider，并注入模拟的IAuthenticationService：

// 模拟IAuthenticationService，配置SignOutAsync的行为
var authServiceMock = new Mock<IAuthenticationService>();
authServiceMock.Setup(s => s.SignOutAsync(
    It.IsAny<HttpContext>(), 
    It.IsAny<string>(), 
    It.IsAny<AuthenticationProperties>()))
.Returns(Task.CompletedTask);

// 构建服务容器并添加模拟服务
var services = new ServiceCollection();
services.AddSingleton(authServiceMock.Object);
var serviceProvider = services.BuildServiceProvider();

// 配置HttpContext的RequestServices
var httpContextMock = new Mock<HttpContext>();
httpContextMock.Setup(c => c.RequestServices).Returns(serviceProvider);

// 将配置好的HttpContext绑定到控制器
controller.ControllerContext = new ControllerContext { HttpContext = httpContextMock.Object };

方案2：使用DefaultHttpContext替代Moq模拟

DefaultHttpContext虽然无法被Moq，但可以直接配置RequestServices，实现起来更简洁：

// 创建DefaultHttpContext实例
var httpContext = new DefaultHttpContext();

// 模拟IAuthenticationService
var authServiceMock = new Mock<IAuthenticationService>();
authServiceMock.Setup(s => s.SignOutAsync(
    It.IsAny<HttpContext>(), 
    It.IsAny<string>(), 
    It.IsAny<AuthenticationProperties>()))
.Returns(Task.CompletedTask);

// 配置服务容器并绑定到HttpContext
var services = new ServiceCollection();
services.AddSingleton(authServiceMock.Object);
httpContext.RequestServices = services.BuildServiceProvider();

// 绑定到控制器
controller.ControllerContext = new ControllerContext { HttpContext = httpContext };

方案选择 #

• 若你已基于Moq的HttpContext编写了大量测试代码，方案1可以适配现有逻辑，无需大幅修改。
• 若测试逻辑灵活，方案2更简洁，避免了Moq对HttpContext的复杂模拟，减少出错概率。

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