Issues
- 6
- 1
Can we add Assert-PathExists (or at least Assert-FileExists and Assert-DirectoryExists)
#48 opened by Jaykul - 2
- 0
Add options for list of properties to inspect
#36 opened by nohwnd - 1
Make it work correctly on PowerShell 2 and newer
#37 opened by nohwnd - 0
Consider communicating intent via pipeline
#38 opened by nohwnd - 13
Assert-Equivalent
#31 opened by DarkLite1 - 0
- 1
Consider adding <{}> option in message templates to allow execution of arbitrary code
#14 opened by nohwnd - 1
- 10
- 4
Update module with approved verbs
#30 opened by DarkLite1 - 5
Allow combining assertion failures into one
#19 opened by nohwnd - 8
Assert-Equal when Expected is a collection
#23 opened by DarkLite1 - 8
- 1
- 1
- 7
- 5
What names should Assert-Throw parameters have?
#13 opened by nohwnd - 0
Add Assert-ThrowAssertionException
#22 opened by nohwnd - 1
- 3
Assert-Throw doesn't seem to match message
#24 opened by alx9r - 0
Consider adding aliases for assertions
#27 opened by nohwnd - 2
What is the expected behavior of Assert-False?
#8 opened by nohwnd - 1
Assert-Same works incorrectly for value types
#6 opened by nohwnd - 0
Add Dictionary to equivalent
#2 opened by nohwnd - 0
Add hashtable to Equivalent
#1 opened by nohwnd - 1
GitHub Repo Name
#21 opened by dargmuesli - 1
- 3
What is more useful Assert-Throw behavior?
#15 opened by nohwnd - 3
Assert-StringEqual : A positional parameter cannot be found that accepts argument 'bde'
#4 opened by irwins - 1
Not all Module functions are exposed
#3 opened by irwins - 0