Session Title: Test Driven Infrastructure Abstract: Infrastructure as code has already been a well-established practice in the DevOps community. In this session, we would be discovering new infrastructure development technique called Test Driven Infrastructure. This is where infrastructure as code and test driven development could go hand in hand. Test driven infrastructure as a practice is an upcoming radical approach towards developing the modern web infrastructure. Test driven infrastructure enables quality delivery of all kind of infrastructures by enabling Four Amigo discussions involving business, development, testing and operation teams. Thus a consistent and reliable environment is created for our applications across the software development life cycle.

1. Test Driving Infrastructure Anju M Dominic
@AnjuDominic3 LKIN19

2. @AnjuDominic3 LKIN19

3. @AnjuDominic3 LKIN19

4. About me
Founder Author Founder
@AnjuDominic3 LKIN19

5. @AnjuDominic3 LKIN19

6. Strategies for Test driving your infrastructure
Strategy for Test
driving your
infrastructure
Test First
Double loop
TDD
@AnjuDominic3 LKIN19

7. @AnjuDominic3 LKIN19

8. 0
2
4
6
8
10
Cost
QualityTime
Chart Title
UT ST
Ref: Chef Software
@AnjuDominic3 LKIN19

9. A Unit Test
Software App Development
Vs
Infrastructure as a Code
@AnjuDominic3 LKIN19

10. Strategies for Test driving your infrastructure
Strategy for Test
driving your
infrastructure
Test First
Double loop
TDD
@AnjuDominic3 LKIN19

11. Test First Approach
Identify detailed
acceptance
criteria's
Craft the system
level acceptance
tests
Fail all the tests
Develop one
scenario
Ensure the test of
the scenario is
passing
Repeat the process
for remaining
scenarios
@AnjuDominic3 LKIN19

12. Double Loop TDD
Identify high level
acceptance criteria's
Craft system level smoke
tests
Fail all the tests
Develop one scenario
using TDD
•Red
•Green
•Refactor
Ensure the smoke test of
the scenario is passing
Repeat the process for
remaining scenarios until
all are passed
@AnjuDominic3 LKIN19

13. Test First Double loop TDD
Identify detailed
acceptance criteria's
Craft the system level
acceptance tests
Fail all the tests
Develop one scenario
Ensure the test of the
scenario is passing
Repeat the process for
remaining scenarios
Identify high level
acceptance criteria's
Craft system level smoke
tests
Fail all the tests
Develop one scenario using
TDD
Ensure the smoke test of
the scenario is passing
Repeat the process for
remaining scenarios until
all are passed
o More accurate test
o Slow
o Costly
o More Flexible
o Faster
o Cheaper
@AnjuDominic3 LKIN19

14. Double Loop TDD
User story- As an administrator, I want to start a Nginx service so that ……
Fedora Debian Redhat SUSE
System level smoke test Unit test
https://github.com/AnjuMeleth/LKIN.git @AnjuDominic3 LKIN19

15. First Loop
https://github.com/AnjuMeleth/LKIN.git @AnjuDominic3 LKIN19

16. Second Loop
1
2
3
4
5 Refactor
@AnjuDominic3 LKIN19

17. Double Loop TDD : An Output
System level smoke test Unit test Infra as code
https://github.com/AnjuMeleth/LKIN.git @AnjuDominic3 LKIN19

18. Thank You
• https://github.com/AnjuMeleth/LKIN.git
• https://www.linkedin.com/in/anju-dominic/
@AnjuDominic3 LKIN19

19. Unit test Vs System Test in context with Chef
0
1
2
3
4
5
6
7
8
9
10
Economical
QualityTime
Unit Test System test
@AnjuDominic3 LKIN19