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

How to write good tests?

Avatar for Alexander Beletsky Alexander Beletsky
April 12, 2013
Programming
2
320

How to write good tests?

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

Avatar for Alexander Beletsky

Alexander Beletsky

April 12, 2013
Tweet

More Decks by Alexander Beletsky

See All by Alexander Beletsky
Snapshot Testing: Going beyond UI
Avatar for Alexander Beletsky alexbeletsky
1
670
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
220
TDD in JavaScript
Avatar for Alexander Beletsky alexbeletsky
4
850
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
440
Likeastore
Avatar for Alexander Beletsky alexbeletsky
3
130
PaaS in your pocker with Dokku
Avatar for Alexander Beletsky alexbeletsky
7
2.6k
Building Single Page Applications
Avatar for Alexander Beletsky alexbeletsky
9
5.4k
.NET developer in JavaScript world
Avatar for Alexander Beletsky alexbeletsky
1
2.8k
Dynamic web development with Oak
Avatar for Alexander Beletsky alexbeletsky
1
610

Other Decks in Programming

See All in Programming
Microservices Platforms: When Team Topologies Meets Microservices Patterns
Avatar for Chris Richardson cer
PRO
0
230
[堅牢.py #1] テストを書かない研究者に送る、最初にテストを書く実験コード入門 / Let's start your ML project by writing tests
Avatar for Shunsuke KITADA shunk031
11
5.6k
生成AIを活用したリファクタリング実践 ~コードスメルをなくすためのアプローチ
Avatar for raedion raedion
0
110
Flutterアプリ運用の現場で役立った監視Tips 5選
Avatar for Takuma Osada ostk0069
1
500
社内オペレーション改善のためのTypeScript / TSKaigi Hokuriku 2025
Avatar for dachi023 dachi023
1
120
「文字列→日付」の落とし穴 〜Ruby Date.parseの意外な挙動〜
Avatar for sg4k0 sg4k0
0
210
Chart.jsで長い項目を表示するときのハマりどころ
Avatar for yumechi(Motoki Hirao) yumechi
0
150
TypeScriptで設計する 堅牢さとUXを両立した非同期ワークフローの実現
Avatar for Matsumoto Moeka moeka__c
2
1.9k
Querying Design System デザインシステムの意思決定を支える構造検索
Avatar for ikuma-t ikumatadokoro
1
1.2k
知られているようで知られていない JavaScriptの仕様 4選
Avatar for syumai syumai
0
630
Feature Flags Suck! - KubeCon Atlanta 2025
Avatar for Pete Hodgson phodgson
0
150
手軽に積ん読を増やすには？/読みたい本と付き合うには？
Avatar for hideki kinjyo o0h
PRO
1
110

Featured

See All Featured
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
Avatar for Sam Stephenson sstephenson
162
15k
Principles of Awesome APIs and How to Build Them.
Avatar for Keavy McMinn keavy
127
17k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
Avatar for Morgane Peng morganepeng
132
19k
Code Review Best Practice
Avatar for Trisha Gee trishagee
72
19k
Dealing with People You Can't Stand - Big Design 2015
Avatar for Cassini Nazir cassininazir
367
27k
Building Applications with DynamoDB
Avatar for Matt Wood mza
96
6.8k
Become a Pro
Avatar for Speaker Deck speakerdeck
PRO
29
5.6k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
Avatar for Vitaly Friedman smashingmag
253
22k
Helping Users Find Their Own Way: Creating Modern Search Experiences
Avatar for Dan Newman danielanewman
31
3k
How to train your dragon (web standard)
Avatar for Monica Dinculescu notwaldorf
97
6.4k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
Avatar for Marc Duiker marcduiker
34
2.3k
Stop Working from a Prison Cell
Avatar for Chris Michel hatefulcrawdad
272
21k

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