.NET 6集成测试触发两次问题排查求助

我在对ASP.NET Core 6 MVC Web应用做集成测试，测试场景是当请求触发时，应用会在指定目录生成文件。但测试时发现，测试完成后约1秒会额外生成一个内容相同的文件；给代码加上线程号后，两个文件对应不同的线程ID。直接运行应用没有这个问题，用Visual Studio断点只能捕获到第一次文件生成操作。

Web应用项目文件 #

<Project Sdk="Microsoft.NET.Sdk.Web">

    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <Nullable>enable</Nullable>
        <ImplicitUsings>enable</ImplicitUsings>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Mvc.Versioning" Version="5.1.0" />
        <PackageReference Include="Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer" Version="5.1.0" />
        <PackageReference Include="Microsoft.EntityFrameworkCore" Version="6.0.19" />
        <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="6.0.19" />
        <PackageReference Include="Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore" Version="6.0.19" />
        <PackageReference Include="Swashbuckle.AspNetCore" Version="6.5.0" />
    </ItemGroup>

    <PropertyGroup>
        <GenerateDocumentationFile>true</GenerateDocumentationFile>
        <NoWarn>$(NoWarn);1591</NoWarn>
    </PropertyGroup>
    
    <ItemGroup>
        <InternalsVisibleTo Include="MyIntegrationProject" />
    </ItemGroup>
</Project>

集成测试项目文件 #

<Project Sdk="Microsoft.NET.Sdk.Web">

    <PropertyGroup>
        <TargetFramework>net6.0</TargetFramework>
        <ImplicitUsings>enable</ImplicitUsings>
        <Nullable>enable</Nullable>

        <IsPackable>false</IsPackable>
    </PropertyGroup>

    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Mvc.Testing" Version="6.0.19" />
        <PackageReference Include="xunit" Version="2.5.0" />
        <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.6.3" />
        <PackageReference Include="xunit.runner.visualstudio" Version="2.5.0">
            <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
            <PrivateAssets>all</PrivateAssets>
        </PackageReference>
        <PackageReference Include="coverlet.collector" Version="6.0.0">
            <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
            <PrivateAssets>all</PrivateAssets>
        </PackageReference>
    </ItemGroup>

    <ItemGroup>
      <ProjectReference Include="..\MyWebApp.csproj" />
    </ItemGroup>

    <ItemGroup>
      <Content Update="appsettings.Test.json">
        <CopyToOutputDirectory>Always</CopyToOutputDirectory>
      </Content>
    </ItemGroup>

</Project>

自定义WebApplicationFactory #

public class CustomWebApplicationFactory<TProgram> : WebApplicationFactory<TProgram> where TProgram : class
{
    protected override void ConfigureWebHost(IWebHostBuilder builder)
    {
        builder.UseEnvironment("Test");
        builder.ConfigureAppConfiguration((hostContext, configurationBuilder) =>
        {
            Microsoft.AspNetCore.Hosting.IWebHostEnvironment env = hostContext.HostingEnvironment;
            string projectDir = Directory.GetCurrentDirectory();
            string configPath = Path.Combine(projectDir, $"appsettings.{env.EnvironmentName}.json");
            configurationBuilder.AddJsonFile(configPath);
        });

        builder.ConfigureServices((hostContext, servicesCollection) =>
        {
            var dbContextDescriptor = servicesCollection.SingleOrDefault(d => d.ServiceType == typeof(DbContextOptions<MyDbContext>));

            servicesCollection.Remove(dbContextDescriptor);

            var dbConnectionDescriptor = servicesCollection.SingleOrDefault(d => d.ServiceType == typeof(DbConnection));

            servicesCollection.Remove(dbConnectionDescriptor);
            servicesCollection.AddDbContextPool<MyDbContext>(options => options.UseSqlServer(""));
        });

    }
}

测试代码 #

public class MyTests : IClassFixture<CustomWebApplicationFactory<Program>>
{
    private readonly CustomWebApplicationFactory<Program> _factory;

    public MyTests(CustomWebApplicationFactory<Program> factory)
    {
        _factory = factory;
    }

    [Fact]
    public async Task ATest()
    {
        // Arrange
        HttpClient client = _factory.CreateClient();

        // Act
        HttpResponseMessage response = await client.PostAsync("/api/v1.0?id=1", null);

        Assert.Equal(HttpStatusCode.OK, response.StatusCode);
        Assert.Equal("application/json; charset=utf-8", response.Content.Headers.ContentType.ToString());
    }
}

问题成因分析 #

1. WebApplicationFactory的多实例启动逻辑 #

集成测试中，WebApplicationFactory默认会启动后台服务器实例，但测试框架可能额外启动一个实例用于健康检查或服务初始化验证。尤其是当使用AddDbContextPool这类池化服务时，初始化过程可能触发与请求相同的业务逻辑，导致文件重复生成。

2. 池化服务的后台线程触发 #

你在自定义配置中替换了DbContext为池化版本，池化上下文的初始化、预热或清理操作可能在后台线程执行了文件生成代码。由于断点仅附着在测试请求的主线程上，后台线程的操作不会被捕获到。

3. 测试结束后的资源清理触发 #

测试完成后，WebApplicationFactory会销毁服务器实例，部分后台服务或池化资源的收尾逻辑可能意外触发了文件生成。比如DbContext池在释放时执行了与请求处理重叠的操作。

验证建议 #

• 在文件生成代码中添加详细日志（包含请求ID、线程ID、调用栈），确认两次生成的触发源。
• 暂时改用AddDbContext替代AddDbContextPool，测试是否还会出现重复生成。
• 在测试代码中添加2秒延迟后再断言文件数量，确认第二次生成的时机是否在测试结束后。
• 检查API中间件链，排查是否有全局中间件在后台线程执行了文件生成逻辑。

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