#Powershell pester examples install

One called test-pwsh and one called test-posh. If ($Error.Fullyqualifiederrorid -eq 'PesterAssertionFailed') shell: powershell Install-Module -Name Pester -RequiredVersion 5.0.4 -confirm:$false -Force Set-PSRepository psgallery -InstallationPolicy trusted Turns out, GitHub Actions has a solution for that. If you are creating a module that you want to be usable for anyone running PowerShell, you need to run your tests on all platforms available, as well as Windows PowerShell.

However, one flaw here is that we are now running this on PowerShell 7 only, Windows only. Turns out, this works just as you expect it to. I just like the false sense of security by defining -Force 😅 Some of the parameters and switches are probably unnecessary, as the container you get served is completely clean. Run Pester on the directory containing the tests files, in my case it is called tests.

#Powershell pester examples install

Install Pester, make sure nothing stops it from doing so by using -Confirm:$false and -force.

Run a couple of cmdlets inline in PowerShell 7, as defined by the shell selection at the end.Checks-out the repository to our workspace, so we can interact with our code.Runs a job called test-pwsh on the latest available Windows image.Runs on every git push to a branch called main (change this to suite your needs).Just to break it down, here we have an action that: Install-Module -Name Pester -RequiredVersion 5.0.4 -Confirm:$false -Force Run: | Set-PSRepository psgallery -InstallationPolicy trusted