This document discusses the importance of including a test strategy in a DevOps culture and process. It notes that testing strategies should define required inputs, outcomes, risks, schedules, human resources, technology resources, entry criteria, exit criteria, and impact/ROI. The document cautions that manual testing does not fit well in DevOps and advocates remembering different testing types. It provides steps for visualizing a testing strategy and improving feedback loops through retrospectives and identifying gaps.

1. DevOps culture
Include test strategy into developers head

2. About author:
Nick Lototskiy
DevOps TechLead at Namecheap
Professional trainer
Node.js and Golang evangelist

3. DevOps is not role
It is a culture!

6. Test strategy?

7. We have Jenkins and UI test

8. What’s In a Testing Strategy?
• Required Inputs
• Outcomes
• Risks
• Schedule
• Human resources

9. What’s In a Testing Strategy?
• Technology resources
• Entry criteria
• Risks
• Exit criteria
• Impact / ROI

10. Manual Testing Just Doesn’t Fit
in DevOps
There are too lazy!

11. … BUT ...
Needs remember about testing types

12. … AND ...
All remember only this

14. … BUT …
We need to start from

16. … THEN …

18. … Something about Shitty Code…

19. What is good code?
• Complexity
• Comments
• Code coverage
• By lines
• By function/classes
• By branches
• By expression

20. And What ?

22. Testing Anti-patterns In
“DevOps Theater”

23. Automated Testing Without a Strategy Falls Apart

24. The Real Costs of Testing Anti-patterns

25. QA in DevOps
Align Testing Activity with Business Priority

26. From Testing Activity to
Strategy
Frame Your Flow

29. Step 1
Dedicate a wall near your story boards to visualizing your testing strategy,
highlighting where test activities are a critical parts of various feedback loops

30. Step 2
Ask contributors where they need better feedback, more useful vs. more
often; work with testing SMEs to apply “program thinking” to these
improvement projects

31. Step 3
Take an active part in team retrospectives and improvement
sessions; come to the meeting with insights and recommendation

32. Step 4
Highlight gaps in the testing strategy: areas of low coverage and resource
constraints where you have evidence that they contribute to defect escape

33. Step 5
Identify bottlenecks in flow around work centers: feature
teams, long-cycle testing activities, Dev and Ops on fixes

34. Questions?

35. Thank you bro!