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
250
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
0
67
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
4
790
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
10
330
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
3
100
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
8
2k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
9
4.9k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
2.4k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
500

Other Decks in Programming

See All in Programming
127622866eaa739e06f9507aff67be2f?s=48 planeta
0
140
2607469010bfd7a0f0bd7546328cb01d?s=48 uakihir0
1
100
30682a28206e455a1bc57d7d85cd1e14?s=48 shomasegi
3
320
52711e2157a6fed933b0361cc06a6953?s=48 marcelgsantos
2
140
44f37c1fe3a6a56376bb41a338741355?s=48 ahiru
22
8.6k
Cb4d62dd7c1d325863696c45e9b6484d?s=48 yaminoma
2
760
C101832d230db74f754e50126903b991?s=48 shoichiimamura
1
110
127f2573f14072eba29ccb60506663eb?s=48 madai0517
3
270
Aaf94d61dec57d1c3cf2de7c09e472d4?s=48 kariad
3
360
Eac0bf787b5279aca5e699ece096956e?s=48 inamiy
9
930
C95cdabc569dc4c7750d776687f66037?s=48 yutannihilation
0
120
1ec68e792f99c958b8ffbd0aadaa182a?s=48 ikkou
5
620

Featured

See All Featured
11c84dff30266b907714802088852677?s=48 jasonvnalue
80
7.9k
E837d2996f52008ace055a08fbfff992?s=48 frogandcode
121
20k
A415db3ac9e9668acbc1fb36eead84ac?s=48 mthomps
37
2.2k
48c098b6579220a67a6ba949be6e4b5a?s=48 revolveconf
195
9.5k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
494
110k
812e1705ff0f8bc1bcf18587bde687d5?s=48 62gerente
582
200k
9fa239b3154a0169d99ab7bf1422dd12?s=48 marcelosomers
220
14k
C4de88ea47538e4594750e3861a341c8?s=48 brettharned
91
2.8k
8ec1383b240b5ba15ffb9743fceb3c0e?s=48 philnash
3
180
F68cb25ae3e5c2106997454b13b7737d?s=48 brad_frost
154
6.2k
C86443373fbfe92996aa882d0d7a59f8?s=48 imathis
478
150k
E6c6e133e74c3b83f04d2861deaa1c20?s=48 searls
202
35k

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