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
We are happy to announce the release of PowerShell Studio 2021 (v5.8.183). This major release is included as part of the regular update cycle for our subscribers.
New Look
New Icons
We have updated all icons to a new style.…
Read More
Every now and then we get a forum post or an email from a customer bemoaning that PowerShell Studio associates the ‘open’ verb for Windows PowerShell script (.ps1) with itself.
Since the “open” verb is by default not associated with…
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
The v5.6.164 service build introduces Pester integration into PowerShell Studio. For those who are not familiar with the Pester module, it is a testing framework for PowerShell. The module allows you to run unit tests on your scripts and functions.…
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
In How to Run Pester Tests, I talked about the different places that you can put your Pester days and the different ways to run them, including, but not limited to, the Invoke-Pester function. Today, I’ll…
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
