We can notice that there wasn’t an error thrown and also spot-check things afterward.
But if the script is covering 1,000 users, there’s no way that’s going to be feasible.
We need to use test automation, too!
What Is Infrastructure Testing?
One way to automate this kind of testing is with what is loosely called infrastructure testing.
What is infrastructure testing?
Testing a internet Port
One typical example of an infrastructure test is testing a internet port.
Luckily, it’s possible for you to use an existing script from the community called Test-NetworkPort.ps1.
This script can be downloaded from thePowerShell Galleryby running
.
Once downloaded, simply call it by using Test-NetworkPort.ps1 and pass a computer name and port to test.
Depending on if the port is listening or not, this script will returnTrueorFalse.
This script performs a test on the infrastructure listening on a particular port.
If the script returnsTrue, the DNS server DC can fix the name of DC.mylab.local.
If not, it would have returnedFalse.
Conclusion
The examples provided here are just two amongst thousands.
Don’t continue to manually confirm your infrastructure is working as you expect.
Get to building some PowerShell scripts and automate those mundane processes for you!
