从 Azure DevOps 管道中的代码覆盖率分析中排除文件

Tus*_*tel 8 unit-testing code-coverage cobertura azure-devops

我已启用 Cobertura 格式的代码覆盖率,并且尝试从 Azure DevOps 管道中的代码覆盖率分析中排除一些文件(尤其是第 3 方 DLL)。目前,下面是我在管道中得到的输出

在此输入图像描述

这里,第 3 方 DLL 也包含在覆盖率报告中。我想排除所有第 3 方 DLL,例如 FluentAssertion、Microsoft.Azure 等。

下面是我的 YAML 文件中产生上述输出的一些行

- task: VSTest@2
  displayName: 'Run .NET Core Unit Tests $(ucSolution)'
  continueOnError: true
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **\MyApp.*.UnitTests.dll
      !**\*TestAdapter.dll
      !**\obj\**
      !**\ref\**
    searchFolder: '$(System.DefaultWorkingDirectory)'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
    diagnosticsEnabled: true
    rerunFailedTests: true
    rerunFailedThreshold: '10'
    rerunMaxAttempts: '1'
    resultsFolder: '$(build.ArtifactStagingDirectory)\Test\Results\core'
    otherConsoleOptions: '/collect:"Code Coverage;Format=Cobertura"'

- task: PublishCodeCoverageResults@1
  displayName: 'Publish code coverage results'
  inputs:
    codeCoverageTool: Cobertura
    summaryFileLocation: $(build.ArtifactStagingDirectory)/Test/Results/**/**/*.cobertura.xml
Run Code Online (Sandbox Code Playgroud)

谁能建议我如何从分析或代码覆盖率报告中排除第 3 方 DLL?

我非常感谢您提供的任何帮助。

pog*_*ama 9

@Jack 提供的解决方案是使用dotnet test“XPlat 代码覆盖率”。对于vstest“代码覆盖率”,您仍然需要 .runsettings 文件,如下所示:

<?xml version="1.0" encoding="utf-8" ?>
<RunSettings>
  <DataCollectionRunSettings>
    <DataCollectors>
      <DataCollector friendlyName="Code Coverage">
        <Configuration>
          <CodeCoverage>
            <ModulePaths>
              <Exclude>
                <ModulePath>FluentAssertions.*</ModulePath>
                <!-- Add more ModulePath nodes here. -->
              </Exclude>
            </ModulePaths>
          </CodeCoverage>
        </Configuration>
      </DataCollector>
    </DataCollectors>
  </DataCollectionRunSettings>
</RunSettings>
Run Code Online (Sandbox Code Playgroud)

<CodeCoverage>(与其他解决方案相比,请注意额外的节点)

接下来,使用参数引用 vstest 任务中的设置文件,runSettingsFile如下所示:

- task: VSTest@2
  displayName: 'Run .NET Core Unit Tests $(ucSolution)'
  continueOnError: true
  inputs:
    testSelector: 'testAssemblies'
    testAssemblyVer2: |
      **\MyApp.*.UnitTests.dll
      !**\*TestAdapter.dll
      !**\obj\**
      !**\ref\**
    searchFolder: '$(System.DefaultWorkingDirectory)'
    platform: '$(buildPlatform)'
    configuration: '$(buildConfiguration)'
    diagnosticsEnabled: true
    rerunFailedTests: true
    rerunFailedThreshold: '10'
    rerunMaxAttempts: '1'
    resultsFolder: '$(build.ArtifactStagingDirectory)\Test\Results\core'
    otherConsoleOptions: '/collect:"Code Coverage;Format=Cobertura"'
    runSettingsFile: '<PATH/TO/FILE.RUNSETTINGS>'
Run Code Online (Sandbox Code Playgroud)


Jac*_*ack 5

将 .runsettings 文件添加到您的解决方案中,并在测试步骤中引用它。runsettings 文件需要一个ModulePaths, Exclude,ModulePath节点,如下所示:

    <?xml version="1.0" encoding="utf-8" ?>
    <RunSettings>
        <DataCollectionRunSettings>
            <DataCollectors>
                <DataCollector friendlyName="XPlat code coverage">
                    <Configuration>
                        <ModulePaths>
                            <Exclude>
                                <ModulePath>.*FluentAssertions.*</ModulePath>
                            </Exclude>
                        </ModulePaths>
                    </Configuration>
                </DataCollector>
            </DataCollectors>
        </DataCollectionRunSettings>
    </RunSettings>
Run Code Online (Sandbox Code Playgroud)

管道 yaml 中的示例测试任务。您的任务会略有不同,VSTest@2但原理相似。了解我如何为 .net core 测试任务添加参数--settings MyFolder/.runsettings

      - task: DotNetCoreCLI@2
        displayName: 'Tests'
        inputs:
          command: test
          projects: 'MyTestProject.csproj'
          arguments: '--configuration debug --collect:"XPlat Code Coverage" --settings MyFolder/.runsettings'
          publishTestResults: true
          testRunTitle: "Run Tests"
Run Code Online (Sandbox Code Playgroud)

可以在此处找到 Microsoft 文档: https://learn.microsoft.com/en-us/visualstudio/test/customizing-code-coverage-analysis ?view=vs-2022