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
310

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
640
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
210
TDD in JavaScript
Avatar for Alexander Beletsky alexbeletsky
4
840
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
420
Likeastore
Avatar for Alexander Beletsky alexbeletsky
3
130
PaaS in your pocker with Dokku
Avatar for Alexander Beletsky alexbeletsky
7
2.5k
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
600

Other Decks in Programming

See All in Programming
10 Costly Database Performance Mistakes (And How To Fix Them)
Avatar for Andrew Atkinson andyatkinson
0
340
Result型で“失敗”を型にするPHPコードの書き方
Avatar for Takuma Kajikawa kajitack
5
650
脱Riverpod？fqueryで考える、TanStack Queryライクなアーキテクチャの可能性
Avatar for Takuma Osada ostk0069
0
140
Claude Code + Container Use と Cursor で作る ローカル並列開発環境のススメ / ccc local dev
Avatar for Yuichi Maekawa kaelaela
9
5.2k
Deep Dive into ~/.claude/projects
Avatar for Yuya Hirayama hiragram
14
2.5k
dbt民主化とLLMによる開発ブースト ~ AI Readyな分析サイクルを目指して ~
Avatar for yosh_yumyum yoshyum
3
1k
RailsGirls IZUMO スポンサーLT
Avatar for 16bit_idol 16bitidol
0
180
すべてのコンテキストを、 ユーザー価値に変える
Avatar for Michiru Kato applism118
3
1.3k
ニーリーにおけるプロダクトエンジニア
Avatar for Nealle nealle
0
840
0626 Findy Product Manager LT Night_高田スライド_speaker deck用
Avatar for Mana Takada mana_takada
0
170
The Modern View Layer Rails Deserves: A Vision For 2025 And Beyond @ RailsConf 2025, Philadelphia, PA
Avatar for Marco Roth marcoroth
1
110
Quand Symfony, ApiPlatform, OpenAI et LangChain s'allient pour exploiter vos PDF : de la théorie à la production…
Avatar for Ahmed EBEN HASSINE ahmedbhs123
0
190

Featured

See All Featured
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
Avatar for Vitaly Friedman smashingmag
251
21k
BBQ
Avatar for Matthew Crist matthewcrist
89
9.7k
For a Future-Friendly Web
Avatar for Brad Frost brad_frost
179
9.8k
Balancing Empowerment & Direction
Avatar for Lara Hogan lara
1
430
Sharpening the Axe: The Primacy of Toolmaking
Avatar for Bryan Cantrill bcantrill
44
2.4k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
Avatar for Tammy Everts tammyeverts
53
2.9k
Designing for humans not robots
Avatar for Tammie Lister tammielis
253
25k
A designer walks into a library…
Avatar for Paul Jervis Heath pauljervisheath
207
24k
Fantastic passwords and where to find them - at NoRuKo
Avatar for Phil Nash philnash
51
3.3k
Building an army of robots
Avatar for Kyle Neath kneath
306
45k
Building Better People: How to give real-time feedback that sticks.
Avatar for Will Jessup wjessup
367
19k
Facilitating Awesome Meetings
Avatar for Lara Hogan lara
54
6.4k

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