06ab3b189d
* Improve path completion * Update src/System.Management.Automation/engine/CommandCompletion/CompletionCompleters.cs Co-authored-by: Steve Lee <slee@microsoft.com> * Address initial feedback from Steve and Paul * Apply suggestions from code review Co-authored-by: Paul Higinbotham <paulhi@microsoft.com> * Apply suggestions from code review Co-authored-by: Ilya <darpa@yandex.ru> * Apply suggestions from iSazonov. * Add missing period to comment. * Add comment explaining limitations of current approach. * Correct some escaping issues and add tests --------- Co-authored-by: Steve Lee <slee@microsoft.com> Co-authored-by: Paul Higinbotham <paulhi@microsoft.com> Co-authored-by: Ilya <darpa@yandex.ru>
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.