InvokePester

InvokePester is the primary command in the Pester testing framework for PowerShell used to execute tests written with Pester’s behavior-driven style. It runs tests defined with Describe, Context, and It blocks, which are typically organized across one or more script files or directories. The command can operate on individual scripts, entire folders, or test blocks loaded in memory, making it suitable for both small units and larger module test suites.

When invoked, InvokePester discovers the tests in the specified location and executes them, applying any filters or tags as needed. It supports running subsets of tests by name or by tags, and it can execute tests across multiple files and folders in a single run. The command is designed to integrate into PowerShell development workflows and to work well in local environments as well as in continuous integration pipelines.

Output and results from InvokePester are designed to be consumable by both humans and automation systems. The command returns a result object that includes the test outcomes and can be used to drive CI logic or to generate reports. In addition to console output, Pester typically provides options for exporting results to files or integrating with reporting tools, enabling transparent visibility into test status and failures.

Typical usage patterns include running all tests within a project by pointing InvokePester at a tests directory, running tests within a specific file, or narrowing execution to tests with particular names or tags. This makes it a versatile tool for validating PowerShell scripts, modules, and automation workflows.

See also: Pester, PowerShell, test automation, continuous integration.