The document discusses test driven infrastructure using tools like Serverspec, Terraform, and Kitchen CI. It begins with an introduction to infrastructure as code and test driven development. It then explains the importance of infrastructure testing and outlines goals like automating configuration, enabling version control, and ensuring solutions work in production. The talk demonstrates how to set up Serverspec test suites to validate expectations for resources and integrate testing with Jenkins. The overall message is that testing infrastructure in a consistent, repeatable manner helps catch bugs early and ensures confidence in automation.

1. By: Adedayo Akinpelu
DelEx Conference
Minsk—Belarus
February 2019
Test Driven Infrastructure
with Serverspec, Terraform
& Kitchen CI

2. By: Adedayo Akinpelu
DelEx Conference
Minsk—Belarus
February 2019
About Nigeria

4. Population: 190million
Tech Ecosystem: $400 Billion
Tech Jobs: over 11%
Tech Companies: 300+

6. 6
Adedayo Akinpelu
DevOps & Site Reliability Engineer.
Writer @ DevOps Nigeria
Organizer - Devops Lagos and
Devops Nigeria Meetup

7. Our Talk today
• Infrastructure as Code
• Test Driven Development
• Test Driven Infrastructure
• TDI Tools
• Getting Started with Serverspec &
Kitchen-CI
• Creating Test Suites in Serverspec
• Integrating Serverspec with Jenkins

8. What to expect
from this talk

9. ● Understand the importance of Infrastructure Testing
● Run or Use Serverspec from the command line
● Setup serverspec test suites for different resources

13. Infrastructure as Code

14. Infrastructure as Code (IaC) is an approach to
infrastructure automation based on practices from
software development, it emphasize consistent,
repeatable, routines for provisioning and changing
systems and their configurations
Kief Morris
Infrastructure as Code Book 2016

15. Design Code Test
Infrastrucuture as Code

17. Problem Solution
Manual Setups In Server Automate Configuration across
board
No Version Control, Unable to
track changes
Version Control enable us to track
changes
Non resuable code Code is totally resuable
It works on my Local Machine but
not in Production
It works Everywhere

18. Goals of IAC

19. ● Changes to the system are routine thereby avoiding fear and uncertainty
● Eliminates long boring repetitive tasks
● Easily Define, Provision and manage resources needed
● Gives room for Continuous Improvement
● Solutions to problems are proven through implementing, testing, and measuring rather than
long meetings and random guesses
● Continuous Delivery
○ Code is Repeatable
○ Code is Shareable
○ Code is TestAble
Goals of IaC

20. Design Code Test
Limitations of IaC

21. Test Driven Development

22. Test
Driven
Development
22
TDD
Write
Test
Refa
ctor
Write
Code

23. Test Driven Infrastructure

24. Design CodeTest
Test Driven Infrastructure

26. Why TDI?
❏Fail Early
❏Validate Expectations
❏Platform Migrations
❏Extreme Confidence in your Automation
❏Better Infrastructure Stability
❏Infrastructure Consistency
❏Cross Platform Testing

27. THE RED-GREEN FACTOR CYCLE
Code
the
tests to
pass
Refactor
your
code
Write
failing
tests

28. Serverspec
TerraformRefactor

29. 5 principles of Test Driven
Infrastructure
Paul Duvali of Stelligent

30. 1.Document
2.Test
3.Implementation
4.Versioning
5.Continuous Improvement

32. Recommendations

33. • Keep tests & configurations small
• Between 30 to 100 tests is recommended

34. Some of the tools used for writing Infrastructure Test
Serverspec Test-Kitchen AWSpec
InSpec

36. Why Serverspec???

37. ● Validate Expectations
● Automate your QA
● Fail Early
● Validate your Output
● Build Confidence
Why Serverspec?

38. Serverspec Use Case

39. ● Package Installation
● Command Execution
● Check for Running Processes & Ports
● File permission Setting
● Others
Serverspec Use Cases

42. Kitchen-CI

44. ● https://kitchen.ci/docs/
● Test Orchestrator
● Originated from the Chef Community
● Very Pluggable on all level
● Your Infrastructure deserves test too
About Kitchen-CI

45. Kitchen-CI

52. “with TDD, you express your
intentions twice: once as a test
and once as a production code, if
the two approaches don’t match,
your test fails, and you have
caught a bug”
Martin EtMajer
Founder | GetCloudNative

53. “Test the Outcome not the
implementation”
Martin EtMajer
Founder | GetCloudNative

54. “First do it right, then do it better”
Martin EtMajer
Founder | GetCloudNative

55. Thank You!!!
Email: adedayoakinpelu@gmail.com
Twitter: @haroldsphinx
LinkedIn: www.linkedin.com/in/haroldsphinx
Blog: www.devops.ng
Portfolio: www.adedayoakinpelu.me