This document discusses the importance of testing infrastructure as code. It provides examples of organizations with and without infrastructure as code (IAC) to show the benefits of IAC. These benefits include faster deployment times, increased agility, higher quality, and less downtime. The document outlines different aspects of infrastructure that should be tested, including servers, services, networks, databases, deployments, hybrid environments, access control, and monitoring. It presents an ideal test pyramid with more unit and integration tests than acceptance tests. The goal is to shift infrastructure testing left to catch errors earlier. Overall, the document argues that testing infrastructure as code leads to more reliable deployments and better organizational performance.

1. 1

2. Yahya Poonawala @meetykp
Siddharth Kulkarni @sid_thinketh
FROM QA TO DEV”QA”OPS !

3. THE INFRASTRUCTURE
is
CODE
3

4. 4
WITHOUT IAC
(GAMING COMPANY)
WITH IAC
(AMAZON)
▪ 40 People Involved
▪ Once A Month Deployment
▪ 2 Hours Downtime
▪ Deployment To 60 Servers
▪ Everything Manual
▪ Single Person Can Deploy
▪ Deployment every 11.6 secs
▪ No Downtime
▪ Deployment to 30k servers
▪ Everything automated

5. UNTINTED PHOTO
Use with care.
5

6. IN A NUTSHELL…
6
➢ Faster time to market
➢ Increased organizational agility
➢ Higher quality

7. WHY DO WE NEED TO TEST OUR INFRASTRUCTURE?
➢ High confidence in changes
➢ Quick and immediate feedback
➢ Shorter release cycle for applications
➢ Maintain sanity of the infrastructure
7

8. 8

9. WHAT DO WE NEED TO
TEST??
9

10. CASE STUDY
REQUIREMENTS
➢ Customer is able to visit the site and browse the products
available.
➢ The website should be available 24*7 and should be able to
sustain high traffic.
➢ Products should not be accessible before the launch date.
➢ We want to launch new features on a regular basis.
➢ The administrators should have detailed knowledge of the health
of the system and issues should be resolvable quickly.
10

11. THINK ABOUT THESE DOMAINS!!
 SERVERS AND SERVICES
 NETWORK CONNECTIONS
 DATABASE SETUP
 DEPLOYMENT STRATEGY
 HYBRID INFRASTRUCTURE
 USER MANAGEMENT
 LOGGING AND MONITORING SETUP
11

12. 12
SERVER AND SERVICES

13. 13
UNIT TESTS

14. INTEGRATION TESTS
14

15. ACCEPTANCE TESTS
15

16. 1
6
NETWORK

17. 17
D
A
T
A
B
A
S
E

18. 18
DEPLOYMENTS

19. 1
9
HYBRID INFRA

20. 2
0
IDENTITY & ACCESS CONTROL

21. 21
MONITORING &
LOGGING

22. IDEAL TEST PYRAMID
22
COURTESY : ANAND BAGMAR

23. WHAT DOES MY INFRA TESTING
PYRAMID LOOK LIKE??
23
UNIT TESTS
INTEGRATION TESTS
ACCEPTANCE
TESTS
MANUAL TESTING

24. WHAT DO WE WANT IT
TO LOOK LIKE??

25. AND THE FUTURE…
25

26. REFERENCES
Test-Driven Infrastructure with Chef :
http://shop.oreilly.com/product/0636920030973.do
Infrastructure as Code :
http://shop.oreilly.com/product/0636920039297.do
26

27. yahya.poonawala@gmail.com
sidd.kulk@gmail.com
THANK YOU