Pester.psm1
# Pester # Version: 3.2.0 # Changeset: $moduleRoot = Split-Path -Path $MyInvocation.MyCommand.Path "$moduleRoot\Functions\*.ps1", "$moduleRoot\Functions\Assertions\*.ps1" | Resolve-Path | Where-Object { -not ($_.ProviderPath.Contains(".Tests.")) } | ForEach-Object { . $_.ProviderPath } function Invoke-Pester { <# .SYNOPSIS Invokes Pester to run all tests (files containing *.Tests.ps1) recursively under the Path .DESCRIPTION Upon calling Invoke-Pester. All files that have a name containing "*.Tests.ps1" will have there tests defined in their Describe blocks executed. Invoke-Pester begins at the location of Path and runs recursively through each sub directory looking for *.Tests.ps1 files for tests to run. If a TestName is provided, Invoke-Pester will only run tests that have a describe block with a matching name. By default, Invoke-Pester will end the test run with a simple report of the number of tests passed and failed output to the console. One may want pester to "fail a build" in the event that any tests fail. To accomodate this, Invoke-Pester will return an exit code equal to the number of failed tests if the EnableExit switch is set. Invoke-Pester will also write a NUnit style log of test results if the OutputXml parameter is provided. In these cases, Invoke-Pester will write the result log to the path provided in the OutputXml parameter. Optionally, Pester can generate a report of how much code is covered by the tests, and information about any commands which were not executed. .PARAMETER Path The path where Invoke-Pester begins to search for test files. The default is the current directory. Aliased 'relative_path' for backwards compatibility. .PARAMETER TestName Informs Invoke-Pester to only run Describe blocks that match this name. .PARAMETER EnableExit Will cause Invoke-Pester to exit with a exit code equal to the number of failed tests once all tests have been run. Use this to "fail" a build when any tests fail. .PARAMETER OutputXml The path where Invoke-Pester will save a NUnit formatted test results log file. If this path is not provided, no log will be generated. .PARAMETER Tag Informs Invoke-Pester to only run Describe blocks tagged with the tags specified. Aliased 'Tags' for backwards compatibility. .PARAMETER ExcludeTag Informs Invoke-Pester to not run blocks tagged with the tags specified. .PARAMETER PassThru Returns a Pester result object containing the information about the whole test run, and each test. .PARAMETER CodeCoverage Instructs Pester to generate a code coverage report in addition to running tests. You may pass either hashtables or strings to this parameter. If strings are used, they must be paths (wildcards allowed) to source files, and all commands in the files are analyzed for code coverage. By passing hashtables instead, you can limit the analysis to specific lines or functions within a file. Hashtables must contain a Path key (which can be abbreviated to just "P"), and may contain Function (or "F"), StartLine (or "S"), and EndLine ("E") keys to narrow down the commands to be analyzed. If Function is specified, StartLine and EndLine are ignored. If only StartLine is defined, the entire script file starting with StartLine is analyzed. If only EndLine is present, all lines in the script file up to and including EndLine are analyzed. Both Function and Path (as well as simple strings passed instead of hashtables) may contain wildcards. .PARAMETER Strict Makes Pending and Skipped tests to Failed tests. Useful for continuous integration where you need to make sure all tests passed. .PARAMETER Quiet Disables the output Pester writes to screen. No other output is generated unless you specify PassThru, or one of the Output parameters. .Example Invoke-Pester This will find all *.Tests.ps1 files and run their tests. No exit code will be returned and no log file will be saved. .Example Invoke-Pester ./tests/Utils* This will run all tests in files under ./Tests that begin with Utils and alsocontains .Tests. .Example Invoke-Pester -TestName "Add Numbers" This will only run the Describe block named "Add Numbers" .Example Invoke-Pester -EnableExit -OutputXml "./artifacts/TestResults.xml" This runs all tests from the current directory downwards and writes the results according to the NUnit schema to artifatcs/TestResults.xml just below the current directory. The test run will return an exit code equal to the number of test failures. .EXAMPLE Invoke-Pester -CodeCoverage 'ScriptUnderTest.ps1' Runs all *.Tests.ps1 scripts in the current directory, and generates a coverage report for all commands in the "ScriptUnderTest.ps1" file. .EXAMPLE Invoke-Pester -CodeCoverage @{ Path = 'ScriptUnderTest.ps1'; Function = 'FunctionUnderTest' } Runs all *.Tests.ps1 scripts in the current directory, and generates a coverage report for all commands in the "FunctionUnderTest" function in the "ScriptUnderTest.ps1" file. .EXAMPLE Invoke-Pester -CodeCoverage @{ Path = 'ScriptUnderTest.ps1'; StartLine = 10; EndLine = 20 } Runs all *.Tests.ps1 scripts in the current directory, and generates a coverage report for all commands on lines 10 through 20 in the "ScriptUnderTest.ps1" file. .LINK Describe about_pester #> [CmdletBinding(DefaultParameterSetName = 'LegacyOutputXml')] param( [Parameter(Position=0,Mandatory=0)] [Alias('relative_path')] [string]$Path = ".", [Parameter(Position=1,Mandatory=0)] [Alias("Name")] [string[]]$TestName, [Parameter(Position=2,Mandatory=0)] [switch]$EnableExit, [Parameter(Position=3,Mandatory=0, ParameterSetName = 'LegacyOutputXml')] [string]$OutputXml, [Parameter(Position=4,Mandatory=0)] [Alias('Tags')] [string[]]$Tag, [string[]]$ExcludeTag, [switch]$PassThru, [object[]] $CodeCoverage = @(), [Switch]$Strict, [Parameter(Mandatory = $true, ParameterSetName = 'NewOutputSet')] [string] $OutputFile, [Parameter(Mandatory = $true, ParameterSetName = 'NewOutputSet')] [ValidateSet('LegacyNUnitXml', 'NUnitXml')] [string] $OutputFormat, [Switch]$Quiet ) if ($PSBoundParameters.ContainsKey('OutputXml')) { Write-Warning 'The -OutputXml parameter has been deprecated; please use the new -OutputFile and -OutputFormat parameters instead. To get the same type of export that the -OutputXml parameter currently provides, use an -OutputFormat of "LegacyNUnitXml".' Start-Sleep -Seconds 2 $OutputFile = $OutputXml $OutputFormat = 'LegacyNUnitXml' } $script:mockTable = @{} $pester = New-PesterState -Path (Resolve-Path $Path) -TestNameFilter $TestName -TagFilter ($Tag -split "\s") -ExcludeTagFilter ($ExcludeTag -split "\s") -SessionState $PSCmdlet.SessionState -Strict:$Strict -Quiet:$Quiet Enter-CoverageAnalysis -CodeCoverage $CodeCoverage -PesterState $pester $message = "Executing all tests in '$($pester.Path)'" if ($TestName) { $message += " matching test name '$TestName'" } Write-Screen $message $scriptBlock = { & $args[0] } Set-ScriptBlockScope -ScriptBlock $scriptBlock -SessionState $PSCmdlet.SessionState Get-ChildItem $pester.Path -Filter "*.Tests.ps1" -Recurse | where { -not $_.PSIsContainer } | foreach { $testFile = $_ try { & $scriptBlock $testFile.PSPath } catch { $firstStackTraceLine = $_.ScriptStackTrace -split '\r?\n' | Select-Object -First 1 $pester.AddTestResult("Error occurred in test script '$($testFile.FullName)'", "Failed", $null, $_.Exception.Message, $firstStackTraceLine) $pester.TestResult[-1] | Write-PesterResult } } $pester | Write-PesterReport $coverageReport = Get-CoverageReport -PesterState $pester Show-CoverageReport -CoverageReport $coverageReport Exit-CoverageAnalysis -PesterState $pester if($OutputFile) { Export-PesterResults -PesterState $pester -Path $OutputFile -Format $OutputFormat } if ($PassThru) { #remove all runtime properties like current* and Scope $properties = @( "Path","TagFilter","ExcludeTagFilter","TestNameFilter","TotalCount","PassedCount","FailedCount","SkippedCount","PendingCount","Time","TestResult" if ($CodeCoverage) { @{ Name = 'CodeCoverage'; Expression = { $coverageReport } } } ) $pester | Select -Property $properties } if ($EnableExit) { Exit-WithCode -FailedCount $pester.FailedCount } } function Set-ScriptBlockScope { [CmdletBinding()] param ( [Parameter(Mandatory = $true)] [scriptblock] $ScriptBlock, [Parameter(Mandatory = $true, ParameterSetName = 'FromSessionState')] [System.Management.Automation.SessionState] $SessionState, [Parameter(Mandatory = $true, ParameterSetName = 'FromSessionStateInternal')] $SessionStateInternal ) $flags = [System.Reflection.BindingFlags]'Instance,NonPublic' if ($PSCmdlet.ParameterSetName -eq 'FromSessionState') { $SessionStateInternal = $SessionState.GetType().GetProperty('Internal', $flags).GetValue($SessionState, $null) } [scriptblock].GetProperty('SessionStateInternal', $flags).SetValue($ScriptBlock, $SessionStateInternal, $null) } function Get-ScriptBlockScope { [CmdletBinding()] param ( [Parameter(Mandatory = $true)] [scriptblock] $ScriptBlock ) $flags = [System.Reflection.BindingFlags]'Instance,NonPublic' [scriptblock].GetProperty('SessionStateInternal', $flags).GetValue($ScriptBlock, $null) } Export-ModuleMember Describe, Context, It, In, Mock, Assert-VerifiableMocks, Assert-MockCalled Export-ModuleMember New-Fixture, Get-TestDriveItem, Should, Invoke-Pester, Setup, InModuleScope, Invoke-Mock Export-ModuleMember BeforeEach, AfterEach, Get-MockDynamicParameters, Set-DynamicParameterVariables |