Writing Pester Tests at Scale
summary
Claims concrete fixes for real scaling problems: migrating to Pester v5 breaks old import patterns so tests must load modules in a BeforeAll block; a module once hit 1700 tests and slowed CI so advice covers merging or sharding tests by OS and PowerShell version; concrete bugs include an Invoke-WebRequest unicode bug on Windows PowerShell and dangerous parameter prompts in generated tests; shows a working helper (called PesterGPT) that suggests code and test fixes and CI automation patterns.
AI-written summary · about
chapters (14)
- 0:00Pester tests at scale
- 3:52Minimal Pester tooling
- 5:59Scaling Pester challenges
- 7:00Testable PowerShell code
- 10:56Team contribution guidelines
- 11:40Versioning in testing
- 14:54Unicode compatibility testing
- 17:31PowerShell docs pitfalls
- 19:19Scaffolding tests efficiently
- 20:25Optimizing test speed
- 24:20Automated test generation
- 27:55Live demo: AI test fixing
- 34:56AI in test workflows
- 37:26Q&A
related talks
36mBeyond Pester 101: Applying testing principles to PowerShell
03h 02mPowerShell Unit and Infrastructure Testing
43mBeyond Pester 102: Acceptance testing with PowerShell
41mPesterize Your Code!!
48mHow to Love Unit Testing
37mTesting, Testing, 1...2...3: Using Pester for Infrastructure ...
49mUsing Pester with Test Kitchen to thoroughly test your Chocolatey Packages
49mReal World Lessons from Scaling Test Automation