@matty or just Invoke-Pester

#PowerShell #Testing #Pester

@bjompen oh man.. I assumed they would be a breeze for you! Have you tried it with #pester v5? I honestly haven’t done much with it, but want to implement it into a a module I’m working on as well as a script I have

@Clatent every time I try to fix something or understand something in #pester I end up spending weeks figuring out scopes only to realize I'm not nearly snart enough to understand how pester works.. I'm convinced it's at least 103% black magic involved.

I managed to get Robot Framework to complete a relatively complex #web #automation #Selenium task inside a #Docker container.

I'm relatively confident that the next integration test I use for my personal website will use Robot Framework. It currently uses #PowerShell #Pester tests, but it's hard to beat the readability of Robot Framework.

#Pester #Powershell #vscode set custom rules:

{{WORKSPACE}}.code-workspace:

```
"powershell.scriptAnalysis.settingsPath": ".vscode/analyzersettings.psd1"
```

this (Path to file) won't work directly in .vscode/settings.json
in a per folder setting - must be a worksapce setting.

Pester tests after Packer builds a template. So cool
#hashicorp #packer #powershell #pester

For today's #PowerShell #FridayFun on #twitch, we're going back into #ugit, with a dose of #pester.

https://www.twitch.tv/mrpowershell/

RT @PSConfEU
New member to the #PSConfEU organisers, @nohwnd is our local emissary in Prague for 2023. Well-known in the #PowerShell Community, #Pester maintainer, he can't wait to welcome you all in Czech Republic 👌

Grab your tickets: https://psconf.eu

Another neverending story https://it.martin-walther.ch/

Deployed a lot of ESXi Hosts with #VMware vSphere AutoDeploy in different network zones and vSphere SSO domains.
All settings (DHCP IP reservation, DNS records, BIOS settings, apply and remediate HostProfile, move to the spec. Cluster, assigning licence, etc) is done with #PowerShell and #PowerCLI.

I did build a Framework with #Gitlab and #pipeline with #pester to test and deploy the node-files as Yaml to the selected environment (Test, Int, Prod).
The node.yml contains all the config to deploy an ESXi Host and will be used as inputfile for the workflow-script that orchestrate the deployment.

And now I found a few new ideas, to optimize this workflow.

Another neverending story:

Deployed 8 ESXi Hosts with #VMware vSphere AutoDeploy in 2 different network zones and vSphere domains. All settings (DHCP IP reservation, DNS records, BIOS settings, apply and remediate HostProfile, move to the spec. Cluster, assigning licence, etc) is done with #PowerShell and #PowerCLI.

I build a Framework with #Gitlab and #pipeline with #pester to test and deploy the node-files as Yaml to the selected environment (Test, Int, Prod). The node.yml contains all the config to deploy an ESXi Host and will be used as inputfile for the workflow-script that orchestrate the deployment.

I found a few new ideas, to optimize this workflow. 😀

CarbonBlack you're killing me!
I had this talk with you already, #Pester and #dbatools are not malicious!

Please, I just want to do my work 😭

I usually like change, but not this time. #Pester #PowerShell

BeforeDiscovery {} got me one step closer but I still need to deal with a hashtable what I don't understand.

Are we still supposed to be able to do this with #Pester V5 and #PowerShell?

describe "one" {
BeforeAll {
$array = 1..10
}
context "two" {
$array | foreach-object {
it "three" {
Write-Warning "$_"
1 | Should -BeExactly 1
}
}
}
}

In case you're interested in #tdd with #powershell and #pester -- I put up a quick repository where I do a ping-pong TDD of the String Calculator Kata:

https://github.com/SeanKilleen/pester-tdd-example

#dotnet #testing #automation

In case you're interested in #tdd with #powershell and #pester -- I put up a quick repository where I do a ping-pong TDD of the String Calculator Kata:

https://github.com/SeanKilleen/pester-tdd-example

#dotnet #testing #automation

Ah, sorry. I'll make sure to write Import-Module inside the BeforeAll section.

https://essenceofcode.com/2022/11/17/pester-loading-powershell-modules-for-testing/

#PowerShell #Pester

How to detect that a #PowerShell script or module is being executed by #Pester?

Since version 5 we can do this in our Pester test:
```PowerShell
BeforeAll {
$isPester = $true
}
```

and use it like this in our actual module/script:
`if ( $isPester ) { Write-Log "this is a test" }`