Link
Embed
Share
Beginning
This slide
Copy link URL
Copy link URL
Copy iframe embed code
Copy iframe embed code
Copy javascript embed code
Copy javascript embed code
Share
Tweet
Share
Tweet
Slide 1
Slide 1 text
Test-driven development for Operations Engineers
Slide 2
Slide 2 text
Thomas Krag Infrastructure Engineer, EclecticIQ
Slide 3
Slide 3 text
Kerim Satirli Infrastructure Engineer, OlinData
Slide 4
Slide 4 text
Test-driven development A history lesson
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
We need to be safe to experiment and make mistakes. We feel good when things work smoothly.
Slide 7
Slide 7 text
We need testing to be sure we are doing no harm. - Kent Beck
Slide 8
Slide 8 text
Trust, but verify.
Slide 9
Slide 9 text
Test-driven development For Software Engineers
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
Test-driven development For Operations Engineers
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
RSpec Test Structure
Slide 20
Slide 20 text
describe 'section' do describe target('selector') do it { should have_something } it { should be_something } end end
Slide 21
Slide 21 text
describe 'YUM repositories' do describe yumrepo('epel') do it { should exist } it { should be_enabled } end end
Slide 22
Slide 22 text
No content
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
No content
Slide 25
Slide 25 text
Next steps Get yourself tested
Slide 26
Slide 26 text
https://cltvt.it/tdd-for-ops code examples and slides
Slide 27
Slide 27 text
#tddforops Q&A