Beyond Pester 102: Acceptance testing with PowerShell
summary
Shows concrete acceptance work: writes a Mattermost backend for PoshBot, provisions systems with Docker and ~200 lines of PowerShell (pre-pester), and runs operational and user acceptance tests with Pester, OVF and CI (AppVeyor Travis CI VSTS GitLab CI). Unit/integration suites run in minutes but acceptance runs take an hour or more and required eight VMs in one example. Packages tests as a module, adds inspector metadata and generates readable reports — the automation works end to end.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:09Acceptance Testing
- 1:43Why Do You Even Test
- 9:23The Cleveland Framework
- 9:59Domains
- 14:18Change the Scope of Acceptance Testing To Reduce the Scope of Failure
- 17:56Operational Acceptance Tests
- 18:07The Operational Acceptance Tests
- 18:50Operational Validation
- 21:03Powershell Ovf Framework
- 22:12Get Operation Validation
- 24:01Pushbot To Run Ovf Tests on Demand
- 30:29Uat
- 35:24Testing Powershell Script
- 40:12Local Acceptance Test
related talks
36mBeyond Pester 101: Applying testing principles to PowerShell
43mBeyond Pester 103: Applying a Testing Mindset
39mWriting Pester Tests at Scale
03h 02mPowerShell Unit and Infrastructure Testing
41mPesterize Your Code!!
49mUsing Pester with Test Kitchen to thoroughly test your Chocolatey Packages
48mHow to Love Unit Testing
45mGitHub Actions for Fun and Profit
