The first task is building the code to test for this scenario. If the service is stopped, that's a problem, and you'd like to know about it. To use an example, let's say you have a Windows service that you expect to be running on all of your servers. Pester can test for anything PowerShell can read.
#Powershell pester examples how to#
We won't cover how to write Pester tests in this article, but if you'd like to learn more, I encourage you to check out The Pester Book, written by me, which goes in-depth on Pester and how to build tests.īefore we can begin writing a test, we first need to figure out what it is we're going to test in the first place. This DSL describes the desired state and has the code necessary to check that state and to compare the result.Ī Pester test can be broken down into a hierarchy of components such as a describe block, a context block and an it block. Infrastructure tests in Pester are PowerShell code that's executed by the Pester PowerShell module and built in a specific way, known as a domain-specific language (DSL).
When I run this PowerShell script, does it create the correct user account?.Does that server have the right software installed on it?.But first, what is an "infrastructure test" anyway?Īn infrastructure test is a generic term for any code that you write to test a current state against an expected state. Pester infrastructure tests can run as standalone tests or be integrated into a broader automation workflow.
0 kommentar(er)
