JUGNsk Meetup#9. Mads Opheim: "9 Ways to Test Your Spaghetti Code"

"Test the legacy code as well” has been a mantra for many years now. But how do you actually do that? When stuck with tangled legacy-spaghetti, it may be hard to see the way out. The path from struggling with your spaghetti into doing TDD is shorter than you think.

It's so easy to say that you should test code as you change it, now matter how legacy, but in a real-world project, you need to know some tools and techniques to be able to do that.

Many developers out there struggle with the impression that testing and TDD cannot work on their project. I’ll challenge that view and hopefully prove it wrong for most participants, and share the techniques and tricks I’ve used.

Transcript

1. JUGNsk 9 ways to test your spaghetti code Mads Opheim @MadsOpheim 1
2. добрый день I’m Mads. 2
3. Don’t Repeat Yourself 3
4. Spaghetti code? 4
5. The 9 ways 5
6. 6 1. Test all or Test small
7. 7 2. Set your dependencies
9. Use interfaces 9
11. Singletons 11
12. 3. Package-protect problematic parts 12
14. Tools for your toolbox 14
15. 4. Consider removing final or static 15
16. In general: untangling and looking at one part at a time 16
17. You’re not as smart as you think you are 17
18. Do simple refactorings to get your code under test 18
19. Functional programming for the win 19
20. Well-designed code is testable code 20
21. 21 5. Help your team
22. You’ll forget things 22
23. 6. Run your tests - and care 23
24. 7. Feature toggles 24
25. 8. One mile at a time 25
26. Refactor in separate commits 26
27. 9. Test-driven development 27
28. Test-driven spaghetti 28
29. TDD on legacy code in practice 29
30. Tip 10, 11 and onwards 30
31. 31 The Deadline For Kunngjøring Is Four Weeks()
32. 32 Properties For Namsmann Mainly Follow The Same Rules as Hovedstevnevitne()
33. You’ll do stupid things - and that’s ok 33
34. Be consistent 34
35. Give me more @lisacrispin, @lisihocke, @techgirl1908, @maaretp... 35
36. Key takeaways 36 1. Good code design improves testability 2. TDD on spaghetti code: TDD + test spaghetti code 3. Write tests for you legacy code - you can do it!
37. Thank you! @MadsOpheim mads.opheim@gmail.com 37