Skip to content

Fix Assert-VerifiableMocks silently does not report anything if 'Verifiable' is spelled wrong on one mock#786

Merged
nohwnd merged 6 commits intopester:masterfrom
alx9r:fix-781
Jul 29, 2017
Merged

Fix Assert-VerifiableMocks silently does not report anything if 'Verifiable' is spelled wrong on one mock#786
nohwnd merged 6 commits intopester:masterfrom
alx9r:fix-781

Conversation

@alx9r
Copy link
Copy Markdown
Member

@alx9r alx9r commented Jun 4, 2017

This PR resolves #781 by doing the following:

  • add tests that assert that all non-deprecated, non-internal, public Pester commands use CmdletBinding
  • add [CmdletBinding()] to the signature of those commands that were missing it
  • fix the comment-based help synopsis for Setup to make identifying public vs. Pester-internal more consistent

@nohwnd nohwnd added this to the V4 milestone Jul 25, 2017
@nohwnd nohwnd changed the title Fix 781 Fix Assert-VerifiableMocks silently does not report anything if 'Verifiable' is spelled wrong on one mock Jul 29, 2017
@nohwnd nohwnd merged commit 21a00bb into pester:master Jul 29, 2017
@alx9r
Copy link
Copy Markdown
Member Author

alx9r commented Jul 29, 2017

Thanks @nohwnd.

@alx9r alx9r deleted the fix-781 branch January 18, 2018 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Assert-VerifiableMocks silently does not report anything if 'Verifiable' is spelled wrong on one mock

2 participants