Introduction to Test-kitchen and InSpec
summary
Test Kitchen drives VMs/containers (Vagrant, Docker, OpenStack) to apply Chef/Puppet/Ansible code and then runs InSpec for verification and compliance; examples include multi‑node OpenStack and Ceph cluster tests that spin up 18 VMs using chef-zero to simulate a chef server, run upgrades and integration tests, and then destroy everything. InSpec provides ~80+ resources, JSON/HTML reports and remote SSH/winrm targets; Kitchen integrates with CI, runs tests concurrently, and successfully caught upgrade issues before production.
AI-written summary · about
chapters (29)
- 0:00Introduction
- 0:32Overview
- 0:44About Lance
- 1:06Open Source Lab
- 2:09Infrastructure Code
- 3:30Tools
- 4:55Why Testkitchen
- 7:55Supported Platforms
- 8:11Workflow
- 9:15Installing Testkitchen
- 10:04Common Commands
- 11:12Configuration
- 12:18Chef
- 12:44Running individual tests
- 13:44Integrating with Docker
- 15:18Integrating with Puppet
- 17:06Integrating with Ansible
- 20:09Testing Terraform
- 20:57Multinode testing
- 24:39Inspect
- 25:44Basics
- 28:08Basic test
- 29:03Basic test output
- 29:23Commands
- 30:15Target URI
- 30:47Profiles
- 31:31Community
- 32:50Fixing Issues
- 35:33Summary
related talks
33mMario Star Power Your Infrastructure: Getting the Most Out of InSpec
41mA Year with Chef and InSpec: A Retrospective with Optum
47mTest Driven Infrastructure with Serverspec & Kitchen CI
29mShifting Security and Sanity Left by Testing Terraform with InSpec
33mTest Driven DevOps
41mChef Cookbook Testing Like a Pro
01h 21mTest Driving your Rails Infrastructure with Chef
42mTesting Infrastructure Code using Test-kitchen, Docker and Chef-Zero