Upgrade to Pro — share decks privately, control downloads, hide ads and more …

9 ways to test your spaghetti code

52482b46b478633a2b766bbf36916fd3?s=47 Mads Opheim
May 30, 2019
Technology
0
14

9 ways to test your spaghetti code

From Nordic Testing Days 2019

52482b46b478633a2b766bbf36916fd3?s=128

Mads Opheim

May 30, 2019
Tweet

More Decks by Mads Opheim

See All by Mads Opheim
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
380
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
7
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
13
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
110
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
91
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
38
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
22
52482b46b478633a2b766bbf36916fd3?s=48 madsopheim
0
43

Other Decks in Technology

See All in Technology
61e7dc2e84a1a1c4ac1a8e2c552fee07?s=48 tutsunom
1
230
3e4b321cfe49136ead7cbfcb5d45a8f0?s=48 juunegreiros
0
120
0886c70b5ecf3b0b0ee6500c5e47884d?s=48 ecoopnet
0
200
2102a6b8760bd6f57f672805723dd83a?s=48 line_developers_tw
PRO
0
190
140494d272a4d89883a94fdfdb29dea2?s=48 oracle4engineer
PRO
1
740
Cdf97a1b1b132c56582773c3ba09a3a6?s=48 rakus_dev
0
290
33d6320b53f63f6627508095633cf5ce?s=48 yosuke_matsuura
PRO
0
2.3k
3ed35dce7bdede37814ccbb952cbf026?s=48 techtver
0
220
Fad1e9ed293fc5b3ec7d4abdffeb636f?s=48 auxesis
0
890
953ea92402e87bce54a4a95ed7f54825?s=48 trickstar13
1
190
476e7a02d660b5dd640cb020ec0a9085?s=48 taka66
1
1.7k
88f4e84b94fe07cddbd9e6479d689192?s=48 soudai
16
9k

Featured

See All Featured
1b75d89772b7eea1f6c89fbf362607d9?s=48 moore
129
22k
C9b18d9dff88a9dd2393364c2b3b21bd?s=48 colly
192
14k
B47b288784fda77a94aeb234ca743c24?s=48 keavy
112
15k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
372
43k
1177e050db6bafe62885362edf6e3537?s=48 lauravandoore
446
29k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
449
36k
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
25
1k
4394ceb8b277f35ee3da7030384efb5d?s=48 davidbonilla
75
3.8k
2f5463832ccb768ccb4a1ca3607c27ef?s=48 jacobian
264
20k
F383c6a4dc55e331bbe2987b622cee6b?s=48 stephaniewalter
267
11k
7edec06b5435e0dac07a353b2cc26253?s=48 geeforr
337
30k
245cee81a9c424266e5e401d844ea881?s=48 lara
596
62k

Transcript

  1. Nordic Testing Days 9 ways to test your spaghetti code

    Mads Opheim @MadsOpheim 1

  2. Tere! I’m Mads. I’m a developer 2

  3. Spaghetti code? 3

  4. The 9 ways 4

  5. 5 1. Test all or Test small

  6. 6 2. Set your dependencies

  7. 7

  8. Singletons 8

  9. 3. Package-protect problematic parts 9

  10. Tools for your toolbox 10

  11. 4. Do simple refactorings to get your code under test

    11

  12. In general: untangling and looking at one part at a

    time 12

  13. You’re not as smart as you think you are 13

  14. Well-designed code is testable code 14

  15. 15 5. Help your team

  16. You’ll forget things 16

  17. 6. Run your tests - and care 17

  18. 7. Feature toggles 18

  19. 8. One mile at a time 19

  20. Refactor in separate commits 20

  21. 9. Test-driven development 21

  22. Test-driven spaghetti 22

  23. TDD on legacy code in practice 23

  24. Tip 10, 11 and onwards 24

  25. 25 The Deadline For Kunngjøring Is Four Weeks()

  26. 26 Properties For Namsmann Mainly Follow The Same Rules as

    Hovedstevnevitne()

  27. You’ll do stupid things - and that’s ok 27

  28. Be consistent 28

  29. Give me more @lisacrispin, @lisihocke, @techgirl1908, @maaretp... 29

  30. Key takeaways 30 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!

  31. Thank you! @MadsOpheim mads.opheim@computas.com 31