The “Hey, Scripting Guys!” blog has been retired. There are many useful posts in this blog, so we keep the blog here for historical reference. However, some information might be very outdated and many of the links might not work anymore.
New PowerShell content is being posted to the PowerShell Community blog where members of the community can create posts by submitting content in the GitHub repository.
Summary: Use Pester to safely test script changes to Active Directory.
(image) How can I test my Active Directory script without having it make changes to my live domain?
(image) Use Pester’s mocking feature to test your code without using the actual Active Directory cmdlets.
(image...
Summary: Guest blogger, Dave Wyatt, discusses using Pester to analyze small pieces of Windows PowerShell code.
Note This is a five-part series that includes the following posts:
Before we get into the technical details today, let’s define a few terms. There are several categories of automated...
Summary: Learn how to incorporate Pester into an automated system.
(image) How do I incorporate Pester into an automated system?
(image) Use one of the features in Pester that are built for this purpose: NUnit XML export, -PassThru switch, or the –EnableExit switch ...
Summary: Guest blogger, Dave Wyatt explains how to get information back from Pester.
Note This is a five-part series that includes the following posts:
At the end of yesterday’s post, I showed this brief example of a .Tests.ps1 file:
(image)
Today, we’ll go into more detail about what goes into...
Summary: Learn how to start a Pester test.
(image) How do I run Pester tests?
(image) Place your tests into a file with a name that ends with .Tests.ps1, and then run the Invoke-Pester cmdlet.
(image...