Using Pester with Test Kitchen to thoroughly test your Chocolatey Packages
summary
Sets up Test Kitchen (Chef Workstation + kitchen-pester) to run Pester suites against Chocolatey packages using Vagrant/Hyper‑V, installs Chocolatey during converge, and produces Pester XML that TeamCity parses. Runs ~4,000 tests across four platforms (16,000 total reported), exposes a Windows Server 2022 behavior that broke a file‑locking test, and shows using skip Pester install plus detailed XML output to avoid false‑green results and enable concurrent runs with controlled concurrency.
AI-written summary · about
chapters (9)
- 0:00Session introduction
- 5:54Pester and Test Kitchen
- 9:11Testing with Kitchen and Pester
- 13:44Installing Kitchen and Pester
- 16:54Kitchen configuration
- 23:59Test Kitchen command anatomy
- 28:09Pester verifier setup
- 33:49Running Kitchen commands
- 40:53Q&A
related talks
37mTesting, Testing, 1...2...3: Using Pester for Infrastructure ...
43mBeyond Pester 102: Acceptance testing with PowerShell
39mWriting Pester Tests at Scale
36mBeyond Pester 101: Applying testing principles to PowerShell
41mPesterize Your Code!!
03h 02mPowerShell Unit and Infrastructure Testing
43mBeyond Pester 103: Applying a Testing Mindset
36mIntroduction to Test-kitchen and InSpec