Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
9_ways_to_test_your_spaghetti_code_-_Devoxx_Ukraine.pdf
Search
Mads Opheim
November 23, 2018
0
50
9_ways_to_test_your_spaghetti_code_-_Devoxx_Ukraine.pdf
Mads Opheim
November 23, 2018
Tweet
Share
More Decks by Mads Opheim
See All by Mads Opheim
Modern Java App Development in the Cloud
madsopheim
0
33
IoT Powered by MicroProfile - JFuture
madsopheim
0
450
IoT Powered by MicroProfile - MakeIT
madsopheim
0
19
9 ways to test your spaghetti code
madsopheim
0
25
IoT powered by MicroProfile
madsopheim
0
23
9 ways to test your spaghetti code
madsopheim
0
110
Domain driven design in the real world
madsopheim
0
200
Make your tests tell the story of your domain
madsopheim
0
74
IoT powered by MicroProfile
madsopheim
0
39
Featured
See All Featured
Understanding Cognitive Biases in Performance Measurement
bluesmoon
6
990
Teambox: Starting and Learning
jrom
128
8.4k
Ruby is Unlike a Banana
tanoku
96
10k
Designing for humans not robots
tammielis
247
25k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
119
39k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
20
1.6k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
243
20k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
124
32k
Music & Morning Musume
bryan
41
5.6k
The Pragmatic Product Professional
lauravandoore
24
5.8k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
356
22k
Embracing the Ebb and Flow
colly
79
4.1k
Transcript
Devoxx Ukraine 9 ways to test your spaghetti code Mads
Opheim @MadsOpheim
Goal of this talk: You’ll be inspired and enabled to
test your legacy code 2
What is spaghetti code? 3
Precondition: You are creative The computer is not 4
1. Extract interface 5
6
7 2. Set your dependencies
8
Singletons 9
3. Package-protect problematic parts 10
11
4. Consider removing final 12
Well-designed code is testable code 13
14 5. Help your team
6. Run your tests - and care 15
7. Feature toggles 16
8. One class != one test class 17
9. Test-driven development 18
Test-driven spaghetti 19
Give me more @lisacrispin, @lisihocke, @techgirl1908... 20
Key takeaways 21 1. Good code design improves testability 2.
Short-term sacrifices are ok 3. Write tests for you legacy code - you can do it!
спасибі! 22 @MadsOpheim
[email protected]