* Prettier formatting for ConvertTo-Json output. #2736 This change standardizes JSON output to example given, as well as codemaid and online lint tools. Sample object used for testing: @{ foo = @{ first = 'a' second = 'bbbbbbbb' } barbarbarbar = @{ first = 'a' second = 'bbbbbbbb' NestedArray = @( 'Test3' 'Test4' 'Test5' 3 4 ) NestedObject = @{ MoreObject = 'AnotherObject' TestBool = $true } } array = @( 'Thing1' 'Thing2' ) dan = 15 } | ConvertTo-Json * Updated CoreCLR implementation to use NewtonSoft Indented Formatting I did not change the FullCLR behavior, I was not sure if you meant to revert my changes or to leave it as is in the current pull request. * Added tests that validate pretty Json output. Not sure if there is a better thought on how to implement these. The first two fail against current master, but succeed once this PR is applied. Third test is successful prior and post this PR. * Moved tests and removed extraneous file. Moved pretty/compressed json tests from standalone file into the existing ConvertTo-Json test file. * Updated tests for cross-platform support |
||
---|---|---|
.. | ||
Common | ||
engine | ||
Host | ||
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 "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.