Christoph Bergmeister
bbd48f60e0
* Implement location history feature for Set-Location. This makes it possible to go back to the last directory using 'cd -', which is exactly the same syntax as on Linux shells. * Use an existing stack implementation instead of relying on an environment variable and move logic for 'cd -' into the internal class of SessionState.Path.SetLocation Keep the (additional) setting of an environment for Unix system in case of mixed usage of cd and Set-Location to provide consistency. * Use a bounded stack with a limit of 1000 and adapt tests. Remove setting environment variable on Linux as discussed in PR. * Fix test: use get-location explicitly to avoid subtle difference in the path string (e.g. an additional slash at the end) Make syntax to .net call of environment consistent with surrounding code * Move initialization of _workingLocationHistoryStack into constructor of SessionStateInternal and set the limit to 20 as discussed in PR 5051. * Make new BoundedStack class in engine utils internal
Pester Testing Test Guide
Also see the Writing Pester Tests document.
Running Pester Tests
First, restore the correct version of Pester using Restore-PSPester.
Then, 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.