Hello! So if you know me you know I like testing, and that when it comes to testing in PowerShell the de-facto testing framework to use is Pester. And it’s claim that it is ubiquitous can be backed-up by the fact that it is now packaged in PowerShell. One of the great things about Pester is that you can mock a function; that is, if you call a function within another function you can mock the internal funciton.
Over the last 6 months or so I’ve been using terraform to deploy infrastructure to Azure. Prior to using terraform I was using ARM Templates and publishing them using Azure PowerShell, again for about 6 months. So I reckon I’ve got a reasonable grasp on both technologies and their similarities/differences and their advantages/disadvantages. But one thing I have done for both is run Pester tests post-deploy to verify the deployment was correct.
Hello! Last week we spent some time in the office here getting to grips with Pester. I’ve written some Pester tests in a few projects I’ve got in GitHub, most notably PoshSSDTBuildDeploy (henceforth known as PBD) and have them running in the VSTS CI build here and the Publish build here. So I felt I was quite familiar with Pester testing. But one thing I had missing in my tests was mocking.
Hello! Some weeks ago I got the tests working on the CI build for PoshSSDTBuildDeploy. The tests were a bit of a mish mash, however they sort of did the trick. Thankfully Eugene Niemand came along and very kindly offered to update the tests into Pester tests, and also just generallytidy up the mess. It’s always great to have a second pair of eyes on any code, as it helps it from not being quite so auteured…