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

How to write good tests?

F32f547e66f3b6528376d67fdb67008f?s=47 Alexander Beletsky
April 12, 2013
Programming
2
210

How to write good tests?

Small talk that I gave to @debitoor guys about practices of writing tests.

F32f547e66f3b6528376d67fdb67008f?s=128

Alexander Beletsky

April 12, 2013
Tweet

More Decks by Alexander Beletsky

See All by Alexander Beletsky
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
270
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
0
69
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
4
800
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
10
330
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
3
110
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
8
2k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
9
4.9k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
2.5k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
520

Other Decks in Programming

See All in Programming
85401912c23c7d5e656c08e7a751e95c?s=48 cocoatomo
0
170
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
PRO
1
140
7b606c5039f083d13e2d2320ce6ddcfa?s=48 dqneo
0
150
091c8449decb2f3549c695b5f903865a?s=48 sh_akira
3
130
827c50b8ee8994d5feac521f09178d0e?s=48 karosuwindam
0
110
52cc8a838bf44a589d2572833b2dd1b9?s=48 palkan
2
460
1ac5890739d082cd2f2f91e3c1799b4d?s=48 hamakou108
4
540
D07d36d7d3263da869c7d030ba4a64a6?s=48 y__mattu
0
230
5155c9bc5b30d9e2a8fd677695887861?s=48 kaonash
2
1.9k
E0e036f89c14b3e59640318eedf9670b?s=48 bkuhlmann
2
330
9e32efa81b675ecd55c166fb7b0a1890?s=48 clusterinc
0
310
Dbab5e5a1fd54531e1119ede6b3b9e65?s=48 horie1024
2
230

Featured

See All Featured
Af6a12710770ad9a7cfd08c97efd40d3?s=48 pedronauck
652
110k
E76911cbe088e5b850d966de3fc7435b?s=48 robhawkes
53
2.9k
9952dfcd5d338f8a8e7175c8a8f65fb5?s=48 wjessup
340
16k
D09fad3e36ae6841f54820be0e907f7a?s=48 rocio
155
11k
F716e5f737fcfb03f2cf8d1a184f1dbe?s=48 nonsquared
81
3.4k
9cde37f47e4a800ea081ea42de8d749a?s=48 dougneiner
119
8k
32de0bd2ba869609d26fd052a4622778?s=48 cromwellryan
104
6.3k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
166
19k
C51b39fa3c79ccb99dcb8a076bc98287?s=48 brianwarren
82
4.8k
B47b288784fda77a94aeb234ca743c24?s=48 keavy
108
14k
7edec06b5435e0dac07a353b2cc26253?s=48 geeforr
333
29k
C620790ae5bf5b50c245b2e0ef95f338?s=48 deanohume
294
28k

Transcript

  1. How to write good tests?

  2. Honestly, I don’t know

  3. But, there are properties of good tests…

  4. … are written before code

  5. … are running very fast

  6. … are helping to find regressions

  7. Writing unit tests is not about code verification

  8. … it’s about code quality and design

  9. Think different Think TDD

  10. Could TDD be applied to everything?

  11. In short, yes code, requirements, ui

  12. Should TDD be applied to everything?

  13. Probably, no simple tasks, prototypes

  14. There are few techniques of writing tests

  15. Classic school Kent Beck, 90’s Inside-Out design Focusing on logic

    (algorithms)

  16. London school Jason Gorman, 00’s Outside-In design Focusing on collaboration

    Mocks

  17. What about integration tests?

  18. They are slow, hard to write, hard to setup… but

  19. … they usually caught most nasty bugs.

  20. None

  21. Maintaining test driven cycle

  22. None

  23. Acceptance test (PO communication) API (integration) tests Utils (units) tests

  24. Thanks, @alexbeletsky