CODEWITHSUNDEEP
powershellpester
Josh Wright
Josh Wright

Reputation: 586

Pass Variables to Powershell Pester Tests v5

I am at the last stages with my pester tests, but am having issues with the variable scoping. I have quite a few tests and would like use something like Global scoping in order to declare variables such as $ModuleName, $ProjectRoot, and other similar things that are needed in each test.

I have tried using New-Variable -Scope Global and $Global:ModuleName but these don't seem to be visible in the Pester Tests.

I am calling Invoke-Pester from a build.ps1 file which has these declared.

Has anyone seen any good ways to use centrally defined variables, without using $env: variables?

Upvotes: 1

Views: 2095

Answers (1)

Josh Wright
Josh Wright

Reputation: 586

I have found using $Env: variables to be the best approach. Thanks to the BuildHelpers module for showing me this.

This is now what the beginning of my Pester Test looks like:

Describe "Core Module Validation" {
BeforeAll {
    $Script:moduleName = $ENV:BHProjectName
    $Script:modulePath = $ENV:BHModulePath

    Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue

    $Script:manifestTestResult = Test-ModuleManifest -Path $Env:BHPSModuleManifest
    $Script:publicScriptFiles = Get-ChildItem -Path "$modulePath\Public" -Recurse
}

It "should cleanly import Module '$ENV:BHProjectName'" {
    { Import-Module -Name $modulePath -Force } | Should -Not -Throw
}
It "should export one or more functions" {
    Import-Module -Name $modulePath -Force
    Get-Command -Module $moduleName | Measure-Object | Select-Object -ExpandProperty Count | Should -BeGreaterThan 0
}

It "should have a valid PSD1 Module Manifest" {
    { Test-ModuleManifest -Path $ENV:BHPSModuleManifest } | Should -Not -Throw
}

These $Env: variables are set in my build.ps1 file, and are only temporary for the session.

Upvotes: 2

Related Questions