Skip to content

Issues: nohwnd/Assert

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

18 Open 16 Closed
18 Open 16 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Can we add Assert-PathExists (or at least Assert-FileExists and Assert-DirectoryExists)
#48 opened Jan 19, 2021 by Jaykul
1
Format-Nicely from the documentation not exposed
#47 opened Jun 27, 2020 by thorstenkampe
6
Consider communicating intent via pipeline
#38 opened Dec 3, 2018 by nohwnd
Add options for list of properties to inspect
#36 opened Nov 22, 2018 by nohwnd
2 of 8 tasks
Using Assert-Throw to Test Terminating vs Non-Terminating Errors
#32 opened Apr 25, 2018 by pldmgg
1
How are tests involving enumerating types meant to be written? feedback needed
#29 opened Nov 20, 2017 by alx9r
10
Consider adding aliases for assertions maybe
#27 opened Nov 16, 2017 by nohwnd
Get-AssertionMessage should replace tokens without case sensitivity
#26 opened Nov 15, 2017 by nohwnd
Where should I propose Assertions for Nested Exceptions? Here or Pester? on hold
#25 opened Nov 12, 2017 by alx9r
8
Add Assert-ThrowAssertionException feature
#22 opened Aug 21, 2017 by nohwnd Custom assertions
Allow combining assertion failures into one feature
#19 opened Aug 18, 2017 by nohwnd
5
How should non-terminating errors in Assert-Throw behave? feedback needed pilot
#17 opened Aug 3, 2017 by nohwnd
1
Consider using Assert-Error instead of Assert-Throw feedback needed maybe
#16 opened Aug 3, 2017 by nohwnd
7
Consider adding <{}> option in message templates to allow execution of arbitrary code feature
#14 opened Aug 3, 2017 by nohwnd
1
What names should Assert-Throw parameters have? feedback needed
#13 opened Aug 3, 2017 by nohwnd
5
Consider renaming Assert-Same to Assert-ReferenceEqual to avoid confusion feedback needed maybe
#7 opened Jul 31, 2017 by nohwnd
1
Add Dictionary to equivalent feature
#2 opened Jan 29, 2017 by nohwnd
Add hashtable to Equivalent feature
#1 opened Jan 29, 2017 by nohwnd
ProTip! Mix and match filters to narrow down what you’re looking for.