SAPIEN’s PowerShell Studio and PrimalScript products both include integrated Pester testing. In this article, we will cover some changes in the Pester 4 to Pester 5 upgrade.
The most significant change in the release of Pester 5 is that it…
Read More
As you advance in the Code-Run-Debug cycle of a new script towards completion it becomes more of an Correct-Test-Debug cycle. The emphasis clearly shifts from writing new code to testing and correcting existing code.
To make that easier we introduced…
Read More
This blog post will get you started working with Git repositories in either of our SAPIEN editors—PowerShell Studio or PrimalScript.
In the following scenario, I will use an existing Git repository stored in Azure DevOps to demonstrate the process of…
Read More
In a previous blog post we covered some of the SAPIEN Packager script engines to create an executable. Next step is to create the application installer so we can deploy the packaged solution.
We are going to take this further.…
Read More
On Friday, February 24, 2017, I posted the following puzzle on Twitter and Facebook (and here!). We provide a Pester test script and a script with detailed help but no code, and you add the code to the script to…
Read More
Applies to: PowerShell 5.0.10586.122, 5.1.14367, Pester 3.4.0
I’m one of those people who thinks a score of 99% is failing, so I love to see those 100% scores when I use the CodeCoverage parameter of Invoke-Pester.
But, while assembling my…
Read More
Applies to Pester 3.4.0
Like any Windows PowerShell script, a script that contains Pester tests can include parameters. It’s easy enough to run the script and pass parameters and values in the usual way.
But, when you use Invoke-Pester to…
Read More
Applies to: Pester 3.4.0
When you crack open the Pester module, you find the New-Fixture function, which creates a script and test file pair, and the Invoke-Pester function, which runs Pester tests.
But New-Fixture is not the only way to…
Read More