Why Test Infrastructure Code
The cost of untested automation.
Your Roles Are Code Too
A role that installs and configures servers is real software. Like any code, it can have bugs that only surface in production.
The Cost of Untested Automation
An untested role can break hundreds of hosts at once. The blast radius of infrastructure code is far wider than a normal bug.
All lessons in this course
- Why Test Infrastructure Code
- molecule init & the Scenario Layout
- Converge, Verify & the Test Matrix
- Idempotence & Lint in the Pipeline