Testing in Production

Why should you test in production? How should you do it? What it is not and what are the gains from it?

Transcript

1. Testing in Production Why should you do it?
2. Outline • What testing in production is not • Why should you do it • How should you do it
3. Disclaimer
4. @nailor
5. Testing in Production
7. What it is not?
8. It’s not a way to make you care less
9. It’s not the replacement for all the testing
10. It’s not the end of 
 the world.
11. Why should you do it?
12. Let’s have a short quiz
13. Staging environment?
14. Problem free 
 staging environment?
15. Production Staging environment on steroids
16. The environment
17. The data
18. The users
19. How to test in production?
20. (Like steroids, it comes with downsides)
22. You want to limit 
 the blast radius
23. Limiter #1: Feature flags
24. [ ] Feature A
 [x] Feature B
25. Add broken code behind the flag
26. Staged roll-outs
27. Easy to support
28. Limiter #2: Dark load
29. One request Two execution paths One response
30. Real use
 real problems
31. Trickier to implement
32. Limiter #3:
 Easy rollback
33. Knowing that breaking things is not fatal is the key
34. How?
35. Checklists
37. What do you gain?
38. Confidence in your code
39. A / B testing
40. Verifiability of ideas
41. Speed
42. Go and test in production! (Author takes no responsibility for anything)
43. Thank you! jyrki@spotify.com / @nailor