You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new Pester version used CmdLetBinding which results in that we are getting errors where we incorrectly used wrong parameters or made typos.
For example a lot of hits on this error
ParameterBindingException: A parameter cannot be found that matches parameter name 'Scope'.
It's because Scope was used in the Mock command.
Mock -CommandName Connect-SQL -MockWith $mockConnectSqlVersion12 -Verifiable -Scope It
The text was updated successfully, but these errors were encountered:
johlju
added
blocking release
The issue or pull request is blocking the next release. Higher priority than label 'High priority'.
bug
The issue is a bug.
help wanted
The issue is up for grabs for anyone in the community.
easy fix
in progress
The issue is being actively worked on by someone.
and removed
help wanted
The issue is up for grabs for anyone in the community.
labels
Aug 18, 2017
johlju
added a commit
to johlju/SqlServerDsc
that referenced
this issue
Aug 18, 2017
- Changes to xSQLServer
- Fixed typos and the use of wrong parameters in unit tests which was
found after release of new version of Pester (issue #773).
vors
removed
the
blocking release
The issue or pull request is blocking the next release. Higher priority than label 'High priority'.
label
Aug 19, 2017
The new Pester version used CmdLetBinding which results in that we are getting errors where we incorrectly used wrong parameters or made typos.
For example a lot of hits on this error
It's because Scope was used in the Mock command.
The text was updated successfully, but these errors were encountered: