![]() Servers get provisioned or deprovisioned, new applications come online, or old ones fade away into the sunset. If you’re not actively testing your infrastructure, don’t worry, your users WILL let you know when it’s not working :) Your infrastructure is not a static object never changing and forever in the state you expect. ![]() What about your Infrastructure?ĭo you test your infrastructure to verify it is working the way you expect?Īre your services configured according to your specifications? PESTER TESTING CODEOr I should say, your users are testing your code for you. Your traditional Windows administrator using PowerShell to automate their jobs away (you won’t) SHOULD test their code.Įven if you’re not writing tests in Pester, RSpec, SpecFlow, etc, you are testing your code. Your traditional developer working with C# or Java tests their code. The fact that we write PowerShell code that defines or runs IT infrastructure is not any different than a web developer using CSS, JavaScript, and HTML, or a full-stack ninja rockstar slinging micro-services written in Go on Kubernetes.Įverything involves working with code therefore everyone is a developer. If you write production code to automate your infrastructure, then you are not a Systems Engineer or Administrator, a SharePoint Engineer or anything else, you are a developer. ![]() I say Infrastructure Developer because that is what we are. In any case, Pester is THE testing framework for PowerShell and is a must-have tool in your Infrastructure Developer toolbox. ![]() If not, then you’re probably living in a strange parallel universe where the Zune is still a thing. If you’ve been using PowerShell for any length of time in the past few years, you have undoubtedly heard of Pester. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |