* Remove BOM, insert newline at EOF * Correct case of $MyInvocation special variable * Correct case of $OFS special variable * Correct case of $NestedPromptLevel special variable * Correct case of $Matches special variable * Correct case of $LASTEXITCODE special variable * Correct case of $StackTrace special variable * Correct case of $args special variable * Correct case of $this special variable * Correct case of $input special variable * Correct case of $PSCmdlet special variable * Correct case of $error special variable * Correct case of $PSDefaultParameterValues special variable * Correct case of $PSScriptRoot special variable * Correct case of $PWD special variable * Correct case of $null special variable * Correct case of $true special variable * Correct case of $false special variable * Correct case of $PSModuleAutoLoadingPreference special variable * Correct case of $IsLinux special variable * Correct case of $IsMacOS special variable * Correct case of $IsWindows special variable * Correct case of $IsCoreCLR special variable * Correct case of $DebugPreference special variable * Correct case of $VerbosePreference special variable * Correct case of $InformationPreference special variable * Correct case of $ExecutionContext special variable * Correct case of $HOME special variable * Correct case of $Host special variable * Correct case of $PID special variable * Correct case of $PSCulture special variable * Correct case of $PSHOME special variable * Correct case of $PSUICulture special variable * Correct case of $PSVersionTable special variable * Fix false positives |
||
---|---|---|
.. | ||
engine | ||
Host | ||
Installer | ||
Language | ||
Modules | ||
Provider | ||
SDK | ||
README.md |
Pester Testing Test Guide
Also see the Writing Pester Tests document.
Running Pester Tests
Go to the top level of the PowerShell repository and run: Start-PSPester
inside a self-hosted copy of PowerShell.
You can use Start-PSPester -Tests SomeTestSuite*
to limit the tests run.
Testing new powershell
processes
Any launch of a new powershell
process must include -noprofile
so that
modified user and system profiles do not causes tests to fail. You also must
take care to call the development copy of PowerShell, which is not the first
one on the path.
Example:
$powershell = Join-Path -Path $PsHome -ChildPath "pwsh"
& $powershell -noprofile -command "ExampleCommand" | Should Be "ExampleOutput"
Portability
Some tests simply must be tied to certain platforms. Use Pester's
-Skip
directive on an It
statement to do this. For instance to run
the test only on Windows:
It "Should do something on Windows" -Skip:($IsLinux -Or $IsMacOS) { ... }
Or only on Linux and OS X:
It "Should do something on Linux" -Skip:$IsWindows { ... }
Pending
When writing a test that should pass, but does not, please do not skip or delete
the test, but use It "Should Pass" -Pending
to mark the test as pending, and
file an issue on GitHub.