Pester - The ubiquitous test and mock framework for PowerShell
Build Server Integration Pester integrates nicely with TFS, Azure, Github, Jenkins and other CI servers, allowing you to fully automate your development lifecycle.
Quick Start | Pester
Pester provides a framework for writing and running tests. Pester is most commonly used for writing unit and integration tests, but it is not limited to just that.
Installation and Update | Pester
Pester is a cross-platform PowerShell module for testing your PowerShell code. Follow these steps to install or update your Pester-module to get started today
Assertion Reference | Pester
Introduction to the built-in assertion operators in Pester to get you started with the most common scenarios
Mock | Pester
For more information, see about_CommonParameters. INPUTS OUTPUTS NOTES RELATED LINKS https://pester.dev/docs/v5/commands/Mock https://pester.dev/docs/v5/usage/mocking …
Data driven tests | Pester
Pester can generate tests based on data. This can range from providing multiple examples on a single `It`, to generating whole set of tests based on an external configuration file
Output | Pester
Pester supports CI-specific output syntaxes to highlight, log and navigate to errors in your tests for a few popular CI systems. This options lets your control how this behavior should work.
Unit Testing within Modules | Pester
With Pester's InModuleScope command, you can cause entire sections of your test script to execute inside the targeted script module. This gives you access to non-exported members of …
Test file structure | Pester
In this file we are using more features of Pester and organize our tests into more groups based on what we are testing. Each group is represented by a Describe or Context block.
Performing Assertions with Should | Pester
This is documentation for Pester v4, which is no longer actively maintained. For up-to-date documentation, see the latest version (v5).