We Still Need to Talk About Infrastructure Testing
summary
Addresses testing infrastructure-as-code at large scale by combining declarative tools (Terraform, Chef) with CI/CD and automated tests rather than simple pings. Recommends using a canary server to apply changes first and run behavior checks (send email, fetch a page, exercise a service), demonstrates TestInfra/Serverspec/InSpec run over SSH, warns about unchecked scripts (e.g., rm -rf bugs) and proposes a layered test pyramid: lint, state, integration, acceptance.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:42Why test infrastructure
- 8:59Dev versus Ops conflict
- 12:50Manual testing problems
- 17:27Infrastructure as code
- 21:00Security and resilience in automation
- 24:12Automated infrastructure tests
- 28:26Future of infrastructure
related talks
28mFrom Monitoring to Automated Testing of Your Infrastructure Code
36mBuild infrastructure as a code (IaC) using test-later...
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
17mTDD for Infrastructure Code
46mInfrastructure testing - it's a real thing!
52mTest Driven Delivery of Infrastructure-As-Code
22mMoving Fast Together: Test-Driven Infrastructure
47mInfrastructure Testing explained