Last time I started exploring how to build a set of Pester tests for code that is written around the .NET Framework. I am using the `Get-OSDetail` function that uses raw .NET classes for CIM objects. In the previous article, I shared the process I used to build the Pester test with the assistance of GitHub CoPilot in VS Code. If you read the last article, you know that the AI-generated code is far from perfect. You still have to know how to write a Pester test. But Copilot did accelerate the process and in many cases provided a good starting point. ## Organizing the Pester Tests When we left off, I had a test that would validate the function's design and input. When Copilot created a test for the `CimSession` parameter, it kindly organized the test in a `Context` block. I often like to organize my tests in this way. It makes it easier to understand the purpose of the test and to run tests selectively.

I added an outer `Context` block for each parameter even though I only have one. If I add more parameters, I can define additional `Context` blocks for each. This also serves as a template for future tests.