API Reference
New-ConfigurationTest
Configures running Pester tests as part of the build.
Remarks
Emits a test configuration segment that instructs the pipeline to run Pester tests after the module is merged/built. Use this when you want builds to fail fast on test failures.
Examples
Enable Pester tests during the build
PS>
New-ConfigurationTest -Enable -TestsPath 'Tests'
Runs tests from the Tests folder after the build/merge step.
Force test execution (ignore caching)
PS>
New-ConfigurationTest -Enable -TestsPath 'Tests' -Force
Useful in CI when you always want a fresh test run.
Common Parameters
This command supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
For more information, see about_CommonParameters.
Syntax
New-ConfigurationTest [-Enable] [-Force] -TestsPath <String> [<CommonParameters>]
#
All Parameter SetsParameters
- Enable SwitchParameter
- Enable test execution in the build.
- Force SwitchParameter
- Force running tests even if caching would skip them.
- TestsPath String
- Path to the folder containing Pester tests.
Outputs
System.Object