* fixes summary block typo * Adds support for Port parameter for SSH PSSessions * Reverted back to master, modified based on PR feedback * Update exception message * remove unused line * Add existing constructor back in as to not break public contract * remove port check * pass nested inner exception straight to Should * dispose runspace after each test * Add SSHHostParameterSet attribute for Invoke-Command Port property * Update ParseSSHConnectionHashTable method to accept Port value as integer * Add helper method for validating port in range. Refactor port parameter constructor overload to use original constructor * rename method * Adds GetSSHConnectionStringParameter and GetSSHConnectionIntParameter methods for retrieving SSHConnection hashtable values * Adds method comments * Adds helper method comment * Change methods to add C# 7 patterns
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 "powershell"
& $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 $IsOSX) { ... }
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.