Add Codecov Support to Repository

This assumes the repository is using the pattern from the Sampler project.

With the release of Pester v4.10 it is now possible to upload the Pester generated JoCoCo file to This is the same file that is used to upload code coverage to Azure Pipelines. needed missing attributes to be part of the JaCoCo XML file. Those attributes that were missing were ignored by Azure Pipelines.

The DSC Community GitHub organization has already added the Codecov GitHub App on all existing repositories in the organization. Also any new repository will have the Codecov GitHub App added automatically.

To upload code coverage to we need to change the build.yaml, add a codecov.yml, and change the stage Test in the file azure-pipelines.yml by modifying the existing unit test job and adding a new job that uploads the coverage.

Modify build.yaml

Because expects the file that is uploaded to be prefixed with JaCoCo we have to change the filename of the JaCoCo test results file that Pester is creating. The file cannot be created with the encoding UTF8 with BOM which is the default on Windows, so we make sure to change the encoding to ascii that accepts.

Under the key Pester add the following keys.

  CodeCoverageOutputFile: JaCoCo_coverage.xml
  CodeCoverageOutputFileEncoding: ascii

NOTE: the filename can be anything after the prefix JaCoCo, for example it is possible to use this JaCoCo_$OsShortName.xml which results in the filename JaCoCO_MacOs.xml when the test task is run on macOS.

Modify azure-pipelines.yml

From the job Test_Unit we can remove the task Set Environment Variables and the task Publish Code Coverage. Those two task will be moved to the new job. Instead we add the task Publish Test Artifact which uploads the test result files that ended up in the folder output/testResults.

Add global variables

At the top of the file, at the same level ass the key trigger add the following.

  buildFolderName: output
  buildArtifactName: output
  testResultFolderName: testResults
  testArtifactName: testResults

Then do a search and replace to change artifactName: 'output' to artifactName: $(buildArtifactName).

Job Test_Unit

The tasks of this job are:

  • Download the build artifact (output that was uploaded by the Build stage)
  • Run the unit tests (which generates the JaCoCo XML file in the folder output/testResults)
  • Uploads the output/testResults folder to the artifact testResults.
      - job: Test_Unit
        displayName: 'Unit'
          vmImage: 'windows-2019'
        timeoutInMinutes: 0
          - task: DownloadBuildArtifacts@0
            displayName: 'Download Build Artifact'
              buildType: 'current'
              downloadType: 'single'
              artifactName: $(buildArtifactName)
              downloadPath: '$(Build.SourcesDirectory)'
          - task: PowerShell@2
            name: test
            displayName: 'Run Unit Test'
              filePath: './build.ps1'
              arguments: "-Tasks test -PesterScript 'tests/Unit'"
              pwsh: false
          - task: PublishTestResults@2
            displayName: 'Publish Test Results'
            condition: succeededOrFailed()
              testResultsFormat: 'NUnit'
              testResultsFiles: '$(buildFolderName)/$(testResultFolderName)/NUnit*.xml'
              testRunTitle: 'Unit (Windows Server Core)'
          - task: PublishBuildArtifacts@1
            displayName: 'Publish Test Artifact'
              pathToPublish: '$(buildFolderName)/$(testResultFolderName)/'
              artifactName: $(testArtifactName)
              publishLocation: 'Container'

Job CodeCoverage

Then we add a new job that depends on the job Test_Unit since we must wait for the JaCoCo XML file to exist. The reason for having a separate job is that we need (or at least it is easiest) to run the upload task in a Linux build worker.

The tasks of this job are:

  • Set environment variables (needed for the upload of Azure Pipelines code coverage)
  • Download the build artifact (output that was uploaded by the Build stage)
  • Download the test artifact (testResults that was upload by the job Test_Unit)
  • Publish code coverage to Azure Pipelines (Azure DevOps)
  • Publish code coverage to
      - job: Code_Coverage
        displayName: 'Publish Code Coverage'
        dependsOn: Test_Unit
          vmImage: 'ubuntu 16.04'
        timeoutInMinutes: 0
          - pwsh: |
              $repositoryOwner,$repositoryName = $env:BUILD_REPOSITORY_NAME -split '/'

              echo "##vso[task.setvariable variable=RepositoryOwner;isOutput=true]$repositoryOwner"
              echo "##vso[task.setvariable variable=RepositoryName;isOutput=true]$repositoryName"
            name: dscBuildVariable
            displayName: 'Set Environment Variables'
          - task: DownloadBuildArtifacts@0
            displayName: 'Download Build Artifact'
              buildType: 'current'
              downloadType: 'single'
              artifactName: $(buildArtifactName)
              downloadPath: '$(Build.SourcesDirectory)'
          - task: DownloadBuildArtifacts@0
            displayName: 'Download Test Artifact'
              buildType: 'current'
              downloadType: 'single'
              artifactName: $(testArtifactName)
              downloadPath: '$(Build.SourcesDirectory)/$(buildFolderName)'
          - task: PublishCodeCoverageResults@1
            displayName: 'Publish Azure Code Coverage'
            condition: succeededOrFailed()
              codeCoverageTool: 'JaCoCo'
              summaryFileLocation: '$(buildFolderName)/$(testResultFolderName)/JaCoCo_coverage.xml'
              pathToSources: '$(Build.SourcesDirectory)/$(buildFolderName)/$(dscBuildVariable.RepositoryName)'
          - script: |
              bash <(curl -s -f "./$(buildFolderName)/$(testResultFolderName)/JaCoCo_coverage.xml"

            displayName: 'Upload to'
            condition: succeededOrFailed()

Add codecov.yml

NOTE: If this file exist and starts with a full stop ., e.g. .codecov.yml, then please rename it to codecov.yml. See this FAQ for more information

These settings can be set as wanted, but the below is the default values that we have used in the DSC modules.

The important part is the key fixes. is expecting the paths in the JaCoCo file to match the folder structure in the GitHub repository. Since the Sampler project runs tests against the built module in the output folder, the paths do not match those of the repository. The key fixes converts the paths in the JaCoCo XML file to the correct paths that expects.

See the codecov.yml Reference for more information about these settings.

  require_ci_to_pass: no
  # master should be the baseline for reporting

  branch: master

  layout: 'reach, diff'
  behavior: default

  range: 50..80
  round: down
  precision: 0

        # Set the overall project code coverage requirement to 70%

        target: 70
        # Set the pull request requirement to not regress overall coverage by more than 5%

        # and let set the goal for the code changed in the patch.

        target: auto
        threshold: 5

  - '\d+\.\d+\.\d+\/::source/'  # move path "X.Y.Z/" => "source/"

Add status badge to

Finally we should add the status badge to the Replace {repositoryName} with the actual repository name, e.g. ComputerManagementDsc.