Automated Infrastructure Testing - Ranjib Dey
Download as PPTX, PDF0 likes1,231 views
The document discusses automated infrastructure testing. It explains that as organizations adopt DevOps practices like continuous integration and delivery, infrastructure needs to be tested and automated just like code. Infrastructure is increasingly defined as code and can be tested at different levels from unit to integration. The document recommends testing infrastructure configurations, monitoring systems to catch failures, and collaborating with operations teams. Automating infrastructure testing helps ensure deployments are reliable and builds battle-tested environments.
![describe_recipe 'nginx:configuration' do
it 'installs version 1.0.15' do
node[:nginx][:version].should == '1.0.15'
file("/etc/nginx/nginx.conf").must_have(:mode, "644")
package("nginx").must_be_installed
service("nginx").must_be_running
end
end](https://image.slidesharecdn.com/automatedinfrastructuretesting-ranjibdey-121102001106-phpapp01-140528232416-phpapp01/85/Automated-Infrastructure-Testing-Ranjib-Dey-37-320.jpg)
Automated Infrastructure Testing - Ranjib Dey
- 1. Automated Infrastructure Testing Ranjib Dey System Administrator, ThoughtWorks
- 2. Part 1 What we are building?
- 3. What you already know?
- 4. To Code (develop functionalities) To Test (ensure if its working fine)
- 5. To Code (develop functionalities) To Test (ensure if its working fine) Automate
- 7. To Code (develop functionalities) To Test (ensure if its working fine) To Deploy (ensure if it can be released)
- 8. To Code (develop functionalities) To Test (ensure if its working fine) To Deploy (ensure if it can be released) Automate
- 9. To Code (develop functionalities) To Test (ensure if its working fine) To Deploy (ensure if it can be released) Automate Automate
- 10. To Code To Test To Deploy Automate Automate CI
- 11. To Code To Test To Deploy Automate Automate CI CD
- 12. Part 2 How it is different?
- 19. Tested code Deployed code Automate Infrastructure Operations Data Compliance End users Integrations
- 21. To Code To Test To Deploy Automate Automate
- 22. To Code To Test To Deploy Automate Automate Build infrastructure
- 23. To Code To Test To Deploy Automate Automate Build infrastructure Production Infrastructure
- 27. Tested code Deployed code Automate Infrastructure as Code Code
- 29. Tested code Deployed code Automate Infrastructure as Code Code Test
- 30. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing
- 32. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing
- 33. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing Functional Testing
- 34. Scenario: Nginx is running as a daemon When I run "ps aux | grep nginx" Then I should see “nginx:master" in the output
- 35. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing Functional Testing
- 36. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing Functional Testing Integration Testing
- 37. describe_recipe 'nginx:configuration' do it 'installs version 1.0.15' do node[:nginx][:version].should == '1.0.15' file("/etc/nginx/nginx.conf").must_have(:mode, "644") package("nginx").must_be_installed service("nginx").must_be_running end end
- 38. Tested code Deployed code Automate Infrastructure as Code Code Test Unit Testing Functional Testing Integration Testing Monitoring
- 39. • Monitoring
- 40. Tested code Deployed code Automate Infrastructure as Code Monitoring Tests Mocks
- 41. Tested code Deployed code Automate Infrastructure as Code Monitoring Tests Mocks Analytics
- 43. Cloud
- 45. I see more code
- 46. I see more code I need more tests
- 47. Cloud AWS
- 49. Oh yeah We love cross browser testing?
- 52. Health of infrastructure Battle tested code
- 53. Health of infrastructure Battle tested code Thorough Monitoring
- 54. • Remember to build feedback system . – Test harness should publish metrics in the same system where ops and project metrics are kept. – Have analytics or trending system on top of the metrics.
- 56. Some advice • Remember MIME types? • World wont be fully automatic ever. Always automate the most time consuming task first. • No easy way out. The function domain requires you to understand man pages, rfps etc. • Choose a text editor rather than an Window manager based IDE.
- 57. References • Infra-automation: http://www.opscode.com/chef/ • Monitoring: http://www.nagios.org/ • Lint tool: http://acrmp.github.com/foodcritic/ • Unit testing: https://github.com/acrmp/chefspec • Functional testing: http://www.cucumber-chef.org/ • Integration testing: https://github.com/calavera/minitest-chef-handler