Pester
Pester copied to clipboard
Pester is the ubiquitous test and mock framework for PowerShell.
## PR Summary Follow-up to #2101 which enabled use of lists when assigning ex. `Run.Path` from hashtable. This PR enables assigning lists to an existing configuration-object, ex `$c.Run.Path = [arraylist]@()`....
## PR Summary Throws an exception when attempting to add a new operator when there's already 32 registered. PowerShell only allows 32 parameter sets due to a `uint`-bitmask used to...
## PR Summary Enables `Should -HaveParameter` to test that a parameter actually exists, but was **not** mandatory and/or did **not** have argument completer. Currently this was only covered by `Should...
## 1. General summary of the issue In the documentation regarding support for mocking of public functions from modules there is a link described as follows: > Note that module...
## PR Summary Throw in `Should -Invoke` when ex. `-Scope Describe` is used while not inside any `Describe`-blocks. Adds regression tests for above scenarios, `-Scope It` while not in `It`...
## General summary of the issue --- in Powershell 7 --- Pester 5 : Invoke-Gherkin not recognized Pester 4.10.0 : Invoke-Gherkin command found but not loaded --- Powershell 5.1.* ---...
## PR Summary Adds support for `-Because` in `-Invoke` and `-InvokeVerifiable` to be able to customize generic mock assert errors. `Should -Invoke` already included the parameter, but the internal method...
### Checklist - [X] Feature request has a meaningful title - [X] I have searched the existing issues. See [all issues](https://github.com/pester/Pester/issues?q=is%3Aissue) - [X] I have tested using the latest version...
# General summary of the issue Error message comparison fails. ## Describe your environment ``` Pester version : 5.1.0-beta1 C:\Users\Chris\Documents\PowerShell\Modules\Pester\5.1.0\Pester.psm1 PowerShell version : 7.1.0 OS version : Microsoft Windows NT...
Default parameter type is figured out in the code, but parameter for it is not surfaced to Should which is unfortunate when you check `$Path = (Get-DefaultPath)` because our assertion...