Pester VS pypy-powershell-install

Pester is what's used for most Powershell testing. While it has some pretty amazing features, it does have issues with .NET class method mocking and sometimes scope can be weird. Here's a simple example:

This is the fun that is Powershell mocking, or at least the form that someone completely new to Powershell would write. One thing I must say is that Pester's mocking capabilities are quite easy to work with. It reminded me of pytest mock patching, only well, simpler. Most of the time spent fighting tests was due to the nuances of pipeline flow. For example, you can see that your mocked method was called X many times through something like this:

The folder blocked all users from reading the files so if you open up the files it looks empty, even tho you have show hidden files turned on. You can't delete it since it says that you need access from TrustedInstaller. This is cleaver by the hacker since trusted installer is actually the name of a windows feature. HOW-EVER by using the command line I found out that the folder contains framework like these two. https://github.com/d1pakda5/PowerShell-for-Pentesters https://github.com/pester/Pester

I'm really surprised that nobody in this thread has mentioned Pester. PowerShell has its own automated unit testing framework that is incredibly versatile. You do need to know PowerShell in order to really make it shine, but if there are some simple tests that your class requires such as "make sure this value conforms to this regex value", Pester is pretty easy to pick up and utilize.

Once you start building code/scripts that are used consistently, consider adding Pester testing to your work. Most sysadmin managers may not get it, but if you're talking to dev managers, they'll absolutely get the importance of unit testing and why it's a good tool to have. Again, down the road. Learn the basics first.

Finally, the Pester testing framework, which ships with Powershell, is a great way to ensure your code actually does what it's meant to do.

Pester GH page

Context "Registry Keys Don't Exist" { BeforeAll { New-Item -Path "TestRegistry:\Software\Python" -Force Mock -CommandName Test-Path -MockWith { return $false } } It "Passes Adds Entries To Registry" { Set-PyPyLauncherEntry -PythonVersion "3.10.12" -PyPyVersion "7.3.12" -InstallPath "C:\PyPy" -RegistryDrive "TestRegistry" $CoreInfo = Get-ItemProperty "TestRegistry:\Software\Python\PyPyInstaller\3.10" $CoreInfo.DisplayName | Should -Be "PyPy 3.10.12" $CoreInfo.SupportUrl | Should -Be "https://github.com/cwgem/pypy-powershell-install" $CoreInfo.Version | Should -Be "7.3.12" $CoreInfo.SysVersion | Should -Be "3.10.12" $CoreInfo.SysArchitecture | Should -Be "64bit" $InstallPathInfo = Get-ItemProperty "TestRegistry:\Software\Python\PyPyInstaller\3.10\InstallPath" $InstallPathInfo.'(default)' | Should -Be "C:\PyPy" $InstallPathInfo.ExecutablePath | Should -Be "C:\PyPy\pypy.exe" $InstallPathInfo.WindowedExecutablePath | Should -Be "C:\PyPy\pypyw.exe" } }

While I had a small bit of Powershell experience I didn't really take it to the full extent. It was mostly done on an as-needed basis. This time though I decided to really take a stab at things. One thing I find interesting is that Powershell feels like more of the UNIX philosophy of gluing commands together than most of what I've done on Linux systems (shove things into a bash script). Even more weird is Powershell being open source. With that said I began my journey with this empty repository. That's because I'm trying to get that sweet code coverage: