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
680
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
230
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
140
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.9k
Dynamic web development with Oak
Avatar for Alexander Beletsky alexbeletsky
1
620

Other Decks in Programming

See All in Programming
AIエージェントのキホンから学ぶ「エージェンティックコーディング」実践入門
Avatar for Masahiro Nishimi masahiro_nishimi
5
450
そのAIレビュー、レビューしてますか？ / Are you reviewing those AI reviews?
Avatar for r-kagaya rkaga
6
4.6k
疑似コードによるプロンプト記述、どのくらい正確に実行される？
Avatar for kokuyouwind kokuyouwind
0
380
カスタマーサクセス業務を変革したヘルススコアの実現と学び
Avatar for Tomoyuki Hamaguchi _hummer0724
0
700
ぼくの開発環境2026
Avatar for yuzneri yuzneri
0
220
フルサイクルエンジニアリングをAI Agentで全自動化したい 〜構想と現在地〜
Avatar for Kaito Minatoya kamina_zzz
0
400
Basic Architectures
Avatar for Denys Poltorak denyspoltorak
0
670
MDN Web Docs に日本語翻訳でコントリビュート
Avatar for uutan1108 ohmori_yusuke
0
650
IFSによる形状設計／デモシーンの魅力 @ 慶應大学SFC
Avatar for がむ gam0022
1
300
360° Signals in Angular: Signal Forms with SignalStore & Resources @ngLondon 01/2026
Avatar for Manfred Steyer manfredsteyer
PRO
0
120
例外処理とどう使い分ける？Result型を使ったエラー設計 #burikaigi
Avatar for Takuma Kajikawa kajitack
16
6.1k
Automatic Grammar Agreementと Markdown Extended Attributes
について
Avatar for Kishikawa Katsumi kishikawakatsumi
0
190

Featured

See All Featured
Agile Leadership in an Agile Organization
Avatar for Dr. Kim W Petersen kimpetersen
PRO
0
80
Building a A Zero-Code AI SEO Workflow
Avatar for Ian Lurie portentint
PRO
0
310
The #1 spot is gone: here's how to win anyway
Avatar for Tamara Novitovic tamaranovitovic
2
940
Design of three-dimensional binary manipulators for pick-and-place task avoiding obstacles (IECON2024)
Avatar for konakalab konakalab
0
350
Reality Check: Gamification 10 Years Later
Avatar for Sebastian Deterding codingconduct
0
2k
How to build an LLM SEO readiness audit: a practical framework
Avatar for Nick Samuel nmsamuel
1
640
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
Avatar for AKADEMIYA2063 akademiya2063
PRO
1
54
Stewardship and Sustainability of Urban and Community Forests
Avatar for Eric Wiseman pwiseman
0
110
Bootstrapping a Software Product
Avatar for Garrett Dimon garrettdimon
PRO
307
120k
Accessibility Awareness
Avatar for Sarah Abderemane sabderemane
0
51
Let's Do A Bunch of Simple Stuff to Make Websites Faster
Avatar for Chris Coyier chriscoyier
508
140k
Are puppies a ranking factor?
Avatar for Jono Alderson jonoalderson
1
2.7k

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