Elevator Pitch
You’ve heard about unit and integration testing with Pester and PowerShell. Now it’s time to turn to the harder topic of Acceptance Testing. What is it?, Why and when should I use it? and what tools can I use?
Description
Previously in “Beyond Pester 101: Applying testing principles to PowerShell” I talked about unit and integration testing with Pester and PowerShell. Now that we’re all experts there, it’s time to tackle Acceptance testing, also known as End to End testing.
Topics:
What is acceptance testing?
- How is it different to unit and integration tests?
- How does pester fit in?
- Difference in testing between Modules, DSC configurations and applications
What am I trying to achieve?
- Remember “Why do I test?”
- Minimal tests for maximum confidence
Part 1 - Creating the systems under test
- For example; Test-Kitchen and Docker
Part 2 - Running the tests
- For example; Pester or OVF
Part 3 - Automating acceptance tests
- Using automated testing systems, for example, Appveyor, Travis CI, VSTS, GitLab CI
Additional considerations
- Instrumentation
- Optimisation
Further information
- Links to other resources
Notes
Each part will contain PowerShell examples and maybe live demos (They tend to take a while so timing may be an issue). In this case pre-recorded demos maybe preferable.