This is just a quick post. As is frequent with these they are as much for me to refer to in the future and also because the very act of writing it down will aid me in remembering. I encourage you to do the same. Share what you learn because it will help you as well as helping others.
Anyway, I was writing some Pester tests for a module that I was writing when I needed some sample data. I have written before about using Json for this purpose This function required some data from a database so I wrote the query to get the data and used dbatools to run the query against the database using Get-DbaDatabase
Simple enough. I wanted to be able to Mock
$variable. I wrapped the code above in a function, let’s call it
Which meant that I could easily separate it for mocking in my test. I ran the code and investigated the $variable variable to ensure it had what I wanted for my test and then decided to convert it into JSON using ConvertTo-Json
Lets show what happens with an example using WideWorldImporters and a query I found on Kendra Littles blogpost about deadlocks
If I investigate the
$variable variable I get
The results were just what I wanted so I thought I will just convert them to JSON and save them in a file and bingo I have some test data in a mock to ensure my code is doing what I expect. However, when I run
$variable | ConvertTo-Json
and thats just for one row!
The way to resolve this is to only select the data that we need. The easiest way to do this is to exclude the properties that we don’t need
$variable | Select-Object * -ExcludeProperty ItemArray, Table, RowError, RowState, HasErrors | ConvertTo-Json
which gave me what I needed and a good use case for -ExcludeProperty