如何在不添加依赖的情况下Mock .NET 8 Azure Function的类库依赖？

一、Mock框架/类库接口的正确姿势 #

你无需引入源项目的全部依赖，只需在测试项目中直接引用对应接口所属的NuGet包即可，这是完全合理的做法：

• IMapper（AutoMapper）：在测试项目安装与源项目同版本的AutoMapper包，直接Mock：

  var mapperMock = new Mock<IMapper>();
  // 按需配置映射行为
  mapperMock.Setup(m => m.Map<DestinationModel>(It.IsAny<SourceModel>()))
            .Returns(new DestinationModel());
  

• IConfiguration：测试项目引用Microsoft.Extensions.Configuration包，有两种实用方式：

  // 方式1：Mock IConfiguration
  var configMock = new Mock<IConfiguration>();
  configMock.Setup(c => c["YourConfigKey"]).Returns("ExpectedValue");
  
  // 方式2：创建内存配置（更贴近真实运行场景）
  var inMemoryConfig = new ConfigurationBuilder()
      .AddInMemoryCollection(new Dictionary<string, string>
      {
          {"YourConfigKey", "ExpectedValue"}
      })
      .Build();
  

• ILogger：测试项目引用Microsoft.Extensions.Logging.Abstractions包，直接Mock即可，若无需验证日志输出，甚至可以用Mock.Of<ILogger<T>>()简化：

  var loggerMock = new Mock<ILogger<ApplicationGovernanceService>>();
  // 验证日志输出示例（按需）
  loggerMock.Verify(l => l.Log(
      LogLevel.Information,
      It.IsAny<EventId>(),
      It.Is<It.IsAnyType>((v, t) => v.ToString().Contains("ExpectedLogMessage")),
      It.IsAny<Exception>(),
      It.IsAny<Func<It.IsAnyType, Exception, string>>()), Times.Once);
  

二、测试项目的依赖注入支持 #

测试项目完全支持依赖注入，推荐用xUnit配合Microsoft.Extensions.DependencyInjection搭建测试容器，示例如下：

public class ApplicationGovernanceServiceTests
{
    private readonly IApplicationGovernanceService _targetService;
    private readonly IServiceProvider _serviceProvider;

    public ApplicationGovernanceServiceTests()
    {
        var services = new ServiceCollection();

        // 注册各依赖的Mock实例或模拟实现
        services.AddSingleton(Mock.Of<IApplicationService>());
        services.AddSingleton(Mock.Of<IApplicationNotificationRepository>());
        services.AddSingleton(Mock.Of<IQueueService>());
        services.AddSingleton(Mock.Of<IMapper>());
        // 使用内存配置替代Mock
        services.AddSingleton(new ConfigurationBuilder()
            .AddInMemoryCollection(new Dictionary<string, string>
            {
                {"AppSettings:Threshold", "10"}
            }).Build());
        services.AddSingleton(Mock.Of<ILogger<ApplicationGovernanceService>>());

        // 注册待测试的服务
        services.AddSingleton<IApplicationGovernanceService, ApplicationGovernanceService>();

        _serviceProvider = services.BuildServiceProvider();
        _targetService = _serviceProvider.GetRequiredService<IApplicationGovernanceService>();
    }

    [Fact]
    public async Task CheckApplicationOwnership_WhenCalled_CompletesSuccessfully()
    {
        // 执行测试方法
        await _targetService.CheckApplicationOwnership();

        // 验证依赖方法调用（按需）
        var appServiceMock = Mock.Get(_serviceProvider.GetRequiredService<IApplicationService>());
        appServiceMock.Verify(s => s.GetAllApplications(It.IsAny<CancellationToken>()), Times.Once);
    }
}

关键提示 #

• 仅引用满足测试需求的最小依赖包，避免引入源项目的冗余依赖，保持测试项目轻量化。
• 对于IConfiguration，内存配置比Mock更能模拟真实配置读取逻辑，适合大多数场景；若仅需验证特定键的读取，Mock更简洁。

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