Writing a small script, waiting to see if it errors out and then eyeballing the results are common. But are you sure that script you created actually did everything you intended? It's important to understand just because a script doesn't output an error and your manual eyeballing sees no problems doesn't actually mean there isn't one. In this course, Infrastructure Testing with Pester, you'll go from guessing the infrastructure changes that you made to seeing if they did actually change. First, you'll discover how to write the right tests. Next, you'll explore the infrastructure dependencies. Finally, you'll learn how to build a web dashboard. By the end of this course, you'll have a better understanding on infrastructure testing with Pester.
Course Overview We all start out scripting things without a lot of discipline. Writing a small script, waiting to see if it errors out, and then eyeballing the results are pretty common, but are you sure that script you created actually did everything you intended? It's important to understand just because a script doesn't output an error, and your manual eyeballing sees no problems, doesn't actually mean there isn't one. It's time to verify your infrastructure is how you intended it to be by building pester tests. In this course you're going to go from guessing the infrastructure changes that you make did what you actually thought they did to actually confirming it. We'll cover everything you need to know from writing the right tests, accounting for things like infrastructure dependencies, and we'll even go over building a beautiful web dashboard to boot.
Implementing Your First Infrastructure Test with Pester Hello. This is Adam Bertram, and this is module 2, Implementing Your First Infrastructure Test with Pester. Now that you've got an introduction to testing in Pester let's dive into what you're really here for, infrastructure testing. In this module we're going to get things set up and build your first infrastructure test. Throughout this course, starting with module 3, we'll be occasionally checking in on George's progress. We'll be doing this once per module, so George is the one building the code. We're just helping him out by confirming his code actually works. This is why you'll see a progress clip in each section. This is where it will be reviewing the code, and we'll be building the actual test for George's script.