Assert
Assert copied to clipboard
nohwnd
A set of advanced assertions for Pester to simplify how you write tests.
See above - the command `Format-Nicely` from the documentation is not available after importing `assert`.
Obviously my thought is that `Assert-PathExists` would have an optional `-PathType` and would work on any provider using Test-Path and turning it into a failure ...
Hi This pull is to replace in part the outdated pull https://github.com/nohwnd/Assert/pull/34. There are 3 things covered here: Commit https://github.com/nohwnd/Assert/commit/c7703405086e8b47f56c43da113ff1ffc748a405 - Moved StrictOrder to Get-EquivalencyOption from Assert-Equivalent so it will...
Use `WMF4` legacy image for testing. Although the image has been enabled, it does not seem to work, maybe it take a bit more time to be enabled.
Consider adding option to Assert-Equivalent that will list the properties to inspect. Also consider adding `-ExcludeProperties`, `OnlyExpectedProperties` or other similar options. - [x] Exclude full paths - [x] Exclude wildcarded...
`Should` & `Assert` use pipeline to pass values to the assertions like this: ```powershell 1,2,3 | Should -HaveType ([int]) ``` This brings problems with enumerating collections if a collection is...
Currently I use `.Replace` to replace the `` and other tokens in `Get-AssertionMessage`. This is unnecessary and should be replaced case-insensitive replacesmen. Eg. with `-replace [regex]::Escape(`.
The templating that is used to generate assertion messages can expand few predefined tokens as well as any token that comes from Data hashtable that is passed to the function....
Hi there - I'm relatively new to Pester (and consequently, new to your Module), but I had a question about how `Assert-Throw` is supposed to work. I've got a PowerShell...
