Deploy Pester Test Suite to CI/CD

When to Use

• User asks to set up CI/CD for Pester tests
• User asks to deploy tests to a pipeline
• User asks about GitHub Actions or Azure DevOps integration
• User mentions automating test runs, coverage gates, or publishing results
• User says "deploy", "pipeline", "CI", "CD", "automate"

Prerequisites

• Pester tests exist in ./tests/ and pass locally
• Source code in ./src/
• Access to GitHub Actions or Azure DevOps pipelines

Step 1: Validate Tests Pass Locally First

Before deploying to CI/CD, verify everything works:

# Install Pester if needed
Install-Module Pester -MinimumVersion 5.5.0 -Force -Scope CurrentUser

# Run with coverage
$config = New-PesterConfiguration
$config.Run.Path = './tests'
$config.Run.Exit = $true
$config.Run.PassThru = $true
$config.CodeCoverage.Enabled = $true
$config.CodeCoverage.Path = './src'
$config.CodeCoverage.CoveragePercentTarget = 90
$config.Output.Verbosity = 'Detailed'
$result = Invoke-Pester -Configuration $config

# Verify
Write-Host "Pass: $($result.PassedCount) | Fail: $($result.FailedCount) | Coverage: check reports/"

If tests fail locally, fix them BEFORE deploying to CI/CD.

Step 2: Choose Pipeline Platform

Option A: GitHub Actions

Read the template: .github/workflows/pester-ci-github.yml

Key features of the template:

• Multi-OS matrix (ubuntu-latest + windows-latest)
• Pester 5.5.0+ installation
• Coverage output: JaCoCo XML → ./reports/coverage.xml
• Test results: NUnit XML → ./reports/test-results.xml
• Artifact upload for test results and coverage
• PR coverage summary comment
• Coverage gate: fails if line coverage < 90%

Customer deploys by copying to their repo's `.github/workflows/`

Option B: Azure DevOps

Read the template: .github/workflows/azure-pipelines.yml.template

Key features of the template:

• Windows agent pool
• PublishTestResults@2 task (NUnit format)
• PublishCodeCoverageResults@2 task (JaCoCo)
• PowerShell coverage gate step
• Variables for testPath, srcPath, reportPath, coverageTarget

Customer deploys by copying to repo root as `azure-pipelines.yml`

Step 3: Configure Coverage Gates

Coverage gates prevent merging code that reduces test quality:

Gate Implementation (PowerShell)

# Parse JaCoCo coverage XML
[xml]$coverage = Get-Content './reports/coverage.xml'
$counters = $coverage.report.counter
$line = $counters | Where-Object { $_.type -eq 'LINE' }
$lineRate = [math]::Round(
    ([int]$line.covered / ([int]$line.covered + [int]$line.missed)) * 100, 1
)

if ($lineRate -lt 90) {
    Write-Error "Coverage $lineRate% is below 90% gate"
    exit 1
}
Write-Host "Coverage gate PASSED: $lineRate%"

Step 4: Configure Test Reports Directory

Ensure reports directory structure:

project/
├── src/          # Source code
├── tests/        # Pester tests
└── reports/      # Generated by CI
    ├── coverage.xml        # JaCoCo format
    └── test-results.xml    # NUnit format

Add to .gitignore:

reports/

Step 5: Set Up Branch Protection (Optional)

GitHub

• Settings → Branches → Branch protection rules
• Require status checks: "Pester Results" must pass
• Require code coverage to not decrease

Azure DevOps

• Project Settings → Repos → Policies → Branch policies
• Add build validation: require pipeline to pass
• Add status check for coverage

Step 6: Verify Pipeline Execution

After deploying:

1. Push a commit or open a PR to trigger the pipeline
2. Verify Pester tests run and pass
3. Verify coverage report is published
4. Verify coverage gate enforces the threshold
5. Verify test results appear in the pipeline UI

Troubleshooting