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_Ukr...
Search
Mads Opheim
November 23, 2018
71
0
Share
9_ways_to_test_your_spaghetti_code_-_Devoxx_Ukraine.pdf
Mads Opheim
November 23, 2018
More Decks by Mads Opheim
See All by Mads Opheim
Modern Java App Development in the Cloud
madsopheim
0
60
IoT Powered by MicroProfile - JFuture
madsopheim
0
610
IoT Powered by MicroProfile - MakeIT
madsopheim
0
43
9 ways to test your spaghetti code
madsopheim
0
52
IoT powered by MicroProfile
madsopheim
0
43
9 ways to test your spaghetti code
madsopheim
0
130
Domain driven design in the real world
madsopheim
0
410
Make your tests tell the story of your domain
madsopheim
0
97
IoT powered by MicroProfile
madsopheim
0
58
Featured
See All Featured
エンジニアに許された特別な時間の終わり
watany
107
240k
Joys of Absence: A Defence of Solitary Play
codingconduct
1
380
Stewardship and Sustainability of Urban and Community Forests
pwiseman
0
210
BBQ
matthewcrist
89
10k
The Curious Case for Waylosing
cassininazir
1
360
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
130
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
47
8.1k
Building Flexible Design Systems
yeseniaperezcruz
330
40k
State of Search Keynote: SEO is Dead Long Live SEO
ryanjones
0
200
Designing for Performance
lara
611
70k
Jess Joyce - The Pitfalls of Following Frameworks
techseoconnect
PRO
1
150
B2B Lead Gen: Tactics, Traps & Triumph
marketingsoph
0
120
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]