InModuleScope
SYNOPSIS
Allows you to execute parts of a test script within the scope of a PowerShell script module.
SYNTAX
DESCRIPTION
By injecting some test code into the scope of a PowerShell script module, you can use non-exported functions, aliases and variables inside that module, to perform unit tests on its internal implementation.
InModuleScope may be used anywhere inside a Pester script, either inside or outside a Describe block.
EXAMPLES
EXAMPLE 1
Normally you would not be able to access "PrivateFunction" from the PowerShell session, because the module only exported "PublicFunction". Using InModuleScope allowed this call to "PrivateFunction" to work successfully.
PARAMETERS
-ModuleName
The name of the module into which the test code should be injected. This module must already be loaded into the current PowerShell session.
-ScriptBlock
The code to be executed within the script module.
-Parameters
{{ Fill Parameters Description }}
-ArgumentList
{{ Fill ArgumentList Description }}
CommonParameters
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
INPUTS
OUTPUTS
NOTES
RELATED LINKS
EDIT THIS PAGE
This page was auto-generated using Pester's comment based help. To edit the content of this page, change the corresponding help in the pester/Pester repository. See our contribution guide for more information.