Continuing the awesome momentum we have gathered with PowerBreakfast, Saturday 5th July graced us with the presence of PowerShell MVP Adam Driscoll. If you didn’t catch it, or if you want to see it again (and many of us do) you can find the recording here. Thanks goes to Milton Goh for making and hosting the recordings. In this session, Adam joins us to talk about Unit Testing for your PowerShell Scripts using Pester. This is something I have been keen to see and to bring to more PowerShell folks, it’s another one of those Developer practices that I am aware of it’s purpose but not really the in’s and out’s of how it works, so to speak. Why is this important? Because as your PowerShell scripts become more complex and ingrained into your Production processes, you need to make sure that when you make changes to them you fully test that they work as expected, you might not always have the access to appropriate infrastructure or environment to do that. This is where Pester is going to help you out. I’d encourage you to check it out and download Pester, have a play. I’ll be doing a post on my experimentation with it quite soon. In the meantime, I am behind on other posts and so forth so I have to get to those! Up next on PowerBreakfast we will be joined by Steven Murawski to talk Desired State Configuration. Even if you’re not using DSC in Production or even soon, now is the time to start that learning curve. We’ll share the date in the coming week or so through the mailing list, if you are not on the list currently you can subscribe here. We hope to see you there.