In my last post I showed you how to write your first Pester test to validate something. Here’s a recap
- Decide the information you wish to test
- Understand how to get it with PowerShell
- Understand what makes it pass and what makes it fail
- Write a Pester Test
You probably have more than one instance that you want to test, so how do you loop through a collection of instances? There are a couple of ways.
Getting the Latest Version of the Module
Steve Jones wrote about getting the latest version of Pester and the correct way to do it. You can find the important information here
The first way is to use the Test Case parameter of the It command (the test) which I have written about when using TDD for Pester here
Lets write a test first to check if we can successfully connect to a SQL Instance. Running
shows us that the
Test-DbaConnection command is the one that we want from the dbatools module. We should always run Get-Help to understand how to use any PowerShell command. This shows us that the results will look like this
So there is a ConnectSuccess result which returns True or false. Our test can look like this for a single instance
which gives us some test results that look like this
which is fine for one instance but we want to check many.
We need to gather the instances into a $Instances variable. In my examples I have hard coded a list of SQL Instances but you can, and probably should, use a more dynamic method, maybe the results of a query to a configuration database. Then we can fill our TestCases variable which can be done like this
Then we can write our test like this
Within the title of the test we refer to the instance inside <> and add the parameter TestCases with a value of the $TestCases variable. We also need to add a Param() to the test with the same name and then use that variable in the test.
This looks like this
Pester is PowerShell
The problem with Test Cases is that we can only easily loop through one collection, but as Pester is just PowerShell we can simply use ForEach if we wanted to loop through multiple ones, like instances and then databases.
I like to use the ForEach method as it is slightly quicker than other methods. It will only work with PowerShell version 4 and above. Below that version you need to pipe the collection to For-EachObject.
Lets write a test to see if our databases have trustworthy set on. We can do this using the Trustworthy property returned from
We loop through our Instances using the ForEach method and create a Context for each Instance to make the test results easier to read. We then place the call to
Get-DbaDatabase inside braces and loop through those and check the Trustworthy property
and it looks like this
So there you have two different ways to loop through collections in your Pester tests. Hopefully this can help you to write some good tests to validate your environment.
Spend a Whole Day With Chrissy & I at SQLBits
If you would like to spend a whole day with Chrissy LeMaire and I at SQLBits in London in February – we have a pre-con on the Thursday
You can find out more about the pre-con sqlps.io/bitsprecon
and you can register at sqlps.io/bitsreg