- Adds -Form Parameter to Invoke-WebRequest and Invoke-RestMethod. - Form Accepts any IDictionary. - Keys are used as multipart/form-data field names (PSObject unwrapped and ConvertTo<String>(Object)). - FileInfo values are added as StreamContent with application/octet-stream content type and the FileInfo.Name as the file name. - Strings are treated as StringContent. - Singe values are converted to string with ConvertTo<String>(Object) and treated as StringContent - Top level collections are enumerated and converted as above. Nested collections are treated as a single value and converted accordingly. - Form is mutually exclusive with -Body and -InFile. - Per PowerShell-Committee decision, -Form makes no assumptions about the HTTP method used. It can theoretically be used with any method. User will need to manually supply -Method POST to post the form. - ContentType and content related headers supplied to -Headers will be ignored/cleared as MultipartFormDataContent requires control of these headers. |
||
---|---|---|
.. | ||
engine | ||
Host | ||
Installer | ||
Language | ||
Modules | ||
Provider | ||
SDK | ||
README.md |
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.