Downloaded 14 times
Uploaded byNathen Harvey
Introduction to Test Kitchen
The document introduces Test Kitchen, a tool for testing infrastructure code. It discusses using Test Kitchen to create and destroy temporary infrastructure that matches production for integration testing. Test Kitchen uses drivers like Vagrant to provision platforms, Chef to run automation code, and InSpec to verify the results by making assertions about system resources. Running the full Test Kitchen workflow helps prevent regressions by testing infrastructure code across platforms before each deployment.
More Related Content
Similar to Introduction to Test Kitchen
Introduction to Test Kitchen
- 1.
- 2.
- 3. @nathenharvey Why Testing? • Movefast with a safety net • Decrease feedback cycles • Increase confidence • Prevent regressions • Scale
- 4. @nathenharvey Developing Infrastructure Automation •Write the automation • Static analysis • Unit testing • Local integration testing Create an infrastructure that matches production Run automation Validate results Destroy • Commit to version control • Submit to pipeline
- 5. @nathenharvey Zoom-in on IntegrationTesting • Create infrastructure that matches production • Run the automation • Verify the results • Destroy the infrastructure
- 6. @nathenharvey Test Kitchen Test harnessto execute infrastructure code on one or more platforms in isolation.
- 7. @nathenharvey The Test Kitchen platforms: -name: ubuntu-16.04 - name: centos-7 platforms
- 8. @nathenharvey The Test Kitchen driver: name:vagrant platforms: - name: ubuntu-16.04 - name: centos-7 kitchen create driver platforms
- 9. @nathenharvey Zoom-in on IntegrationTesting Create infrastructure that matches production • Run the automation • Verify the results • Destroy the infrastructure
- 10. @nathenharvey The Test Kitchen driver: name:vagrant platforms: - name: ubuntu-16.04 - name: centos-7 provisioner: name: chef_zero kitchen create driver platforms kitchen converge provisioner
- 11. @nathenharvey Chef Recipe package 'git'do action :install end
- 12. @nathenharvey Zoom-in on IntegrationTesting Create infrastructure that matches production Run the automation • Verify the results • Destroy the infrastructure
- 14. @nathenharvey InSpec • Open-source framework •Infrastructure testing • Make assertions about state of resources in the infrastructure
- 15. @nathenharvey Sample InSpec code describeservice('apache2') do it { should be_running } end describe port(80) do it { should be_listening } end describe http('http://localhost', enable_remote_worker: true) do its('status') { should cmp 200 } its('body') { should match /Welcome to / } end
- 16. @nathenharvey The Test Kitchen driver: name:vagrant platforms: - name: ubuntu-16.04 - name: centos-7 provisioner: name: chef_zero verifier: name: inspec kitchen create driver platforms kitchen converge provisioner kitchen verify verifier
- 17. @nathenharvey Verify the resultswith InSpec describe package('git') do it { should be_installed } end describe command('git') do it { should exist } end describe command('which git') do its('exit_status') { should eq 0 } end
- 18. @nathenharvey Zoom-in on IntegrationTesting Create infrastructure that matches production Run the automation Verify the results • Destroy the infrastructure
- 19. @nathenharvey The Test Kitchen driver: name:vagrant platforms: - name: ubuntu-16.04 - name: centos-7 provisioner: name: chef_zero verifier: name: inspec kitchen create driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy
- 20. @nathenharvey Zoom-in on IntegrationTesting Create infrastructure that matches production Run the automation Verify the results Destroy the infrastructure
- 21. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test
- 22. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test kitchen destroy
- 23. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test kitchen destroy kitchen create
- 24. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test kitchen destroy kitchen create kitchen converge
- 25. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test kitchen destroy kitchen create kitchen converge kitchen verify
- 26. @nathenharvey The Test Kitchen kitchencreate driver platforms kitchen converge provisioner kitchen verify verifier kitchen destroy kitchen test kitchen destroy kitchen create kitchen converge kitchen verify kitchen destroy
- 27.
- 28. @nathenharvey The Test Kitchen driver: name:kitchen create driver
- 29. @nathenharvey The Test Kitchen provisioner: name: kitchenconverge provisioner
- 30. @nathenharvey The Test Kitchen verifier: name: kitchenverify verifier
- 31. @nathenharvey Get Started withTest Kitchen • Install Chef Development Kit - https://downloads.chef.io/chefdk Test Kitchen InSpec • Install Driver Requirements Vagrant – VirtualBox & Vagrant Docker – Docker GCE – None, but best to Google Cloud SDK installed EC2 – None, but you need an AWS account
- 32. @nathenharvey Use, Share, Contribute! •Test Kitchen https://kitchen.ci/ https://github.com/test-kitchen • InSpec https://www.inspec.io/ https://github.com/chef/inspec • Code from this presentation - https://github.com/nathenharvey/intro-to-test- kitchen
- 33. @nathenharvey Join us onSlack • http://community-slack.chef.io • #general (for Chef stuff) • #test-kitchen • #inspec The Chef community believes that diversity is one of our biggest strengths! YOU are welcome here!
- 34. @nathenharvey What questions canI answer for you? Nathen Harvey VP, Community Development Chef @nathenharvey