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
260
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
0
68
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
4
790
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.4k
F32f547e66f3b6528376d67fdb67008f?s=48 alexbeletsky
1
510

Other Decks in Programming

See All in Programming
5c588fdfe782f92fa6b081903edd82bb?s=48 hr01
0
1.6k
6165f5bae67e249133eba24da4b93780?s=48 trajchevska
2
350
1d5a7a934b466ede82b89a39b1404c0b?s=48 daiki1020
0
1.1k
405fe9ab689473f267e2cfbd95f78c75?s=48 kyonmm
2
2.1k
6a87c9bfc71c805c3f5f248b359365d3?s=48 mu2in
0
140
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
PRO
0
270
4047c64e3a1e2f81addd4ba675ddc451?s=48 zsmb
1
130
2102a6b8760bd6f57f672805723dd83a?s=48 line_developers_tw
1
460
91b77d9a98b86e27838b183407270bc0?s=48 supikiti
3
1.3k
3aae47c11fab74b1db6ec80cd6f49058?s=48 takahi5
0
220
7975b9fd58c8945ae1c6b38747de7f28?s=48 line_developers_tw2
0
680
0ed10d1154c696886ca483fe827cb299?s=48 thatjeffsmith
0
420

Featured

See All Featured
E6c6e133e74c3b83f04d2861deaa1c20?s=48 searls
204
35k
C9b18d9dff88a9dd2393364c2b3b21bd?s=48 colly
186
14k
651dcfe41723207fbb0aa044a4f7c07f?s=48 dotmariusz
94
5.1k
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
27
1.9k
4262b9cfacfb6b2c77f23e1d0310cd3e?s=48 myddelton
109
11k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
494
110k
Af6a12710770ad9a7cfd08c97efd40d3?s=48 pedronauck
652
110k
C1daf20e5c49ff910745198ef9869ac2?s=48 hatefulcrawdad
257
17k
1177e050db6bafe62885362edf6e3537?s=48 lauravandoore
437
28k
0c6fd6a08d0f898159cda7cafcacf07f?s=48 afnizarnur
176
14k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
267
17k
B83d5b590577969ee79a5ad845411a7d?s=48 ammeep
656
54k

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