Skip to content
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.

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

Export Should-Invoke* and Should-HaveParameter #2465

Open
3 tasks done
nohwnd opened this issue May 18, 2024 · 3 comments · May be fixed by #2587
Open
3 tasks done

Export Should-Invoke* and Should-HaveParameter #2465

nohwnd opened this issue May 18, 2024 · 3 comments · May be fixed by #2587
Assignees
Labels
Assertions For issues related with assertions Feature
Milestone

Comments

@nohwnd
Copy link
Member

nohwnd commented May 18, 2024

Checklist

Summary of the feature request

Export existing assertions in the same format as Should-Be, to have complete set of assertions using the new format.

How should it work?

No response

@nohwnd nohwnd added Feature Assertions For issues related with assertions labels May 18, 2024
@nohwnd nohwnd added this to the 6.0.0 milestone May 18, 2024
@fflaten
Copy link
Collaborator

fflaten commented Jul 4, 2024

See relevant comment about positional parameters: #2527 (comment)

@johlju
Copy link
Contributor

johlju commented Jul 13, 2024

Will this issue also handle/track Should -InvokeVerifiable?

@fflaten fflaten changed the title Export Should-Invoke and Should-HaveParameter Export Should-Invoke* and Should-HaveParameter Jul 13, 2024
@fflaten
Copy link
Collaborator

fflaten commented Jul 14, 2024

Should be. I'd suggest a Should-Invoke -Verifiable parameter set to reduce bloat and be consistent with Mock -Verifiable

@nohwnd nohwnd self-assigned this Oct 8, 2024
@nohwnd nohwnd linked a pull request Dec 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Assertions For issues related with assertions Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants