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
340
2

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

More Decks by Alexander Beletsky

See All by Alexander Beletsky
Snapshot Testing: Going beyond UI
Avatar for Alexander Beletsky alexbeletsky
1
710
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
250
TDD in JavaScript
Avatar for Alexander Beletsky alexbeletsky
4
860
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
470
Likeastore
Avatar for Alexander Beletsky alexbeletsky
3
170
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.5k
.NET developer in JavaScript world
Avatar for Alexander Beletsky alexbeletsky
1
2.9k
Dynamic web development with Oak
Avatar for Alexander Beletsky alexbeletsky
1
650

Other Decks in Programming

See All in Programming
ユニットテストの先へ：テスト技法で要求・仕様を整理するJava開発実践 / Beyond_Unit_Testing_Practical_Java_Development_Techniques_for_Organizing_Requirements_and_Specifications
Avatar for SHIMANE, Yoshikazu shimashima35
0
390
エージェンティックRAGにAWSで入門しよう！
Avatar for Har1101 har1101
8
1.5k
AIだと陥りがちなJakarta EE最新技術への移行時の落とし穴と解決策
Avatar for tnagao7 tnagao7
0
100
The NotImplementedError Problem in Ruby
Avatar for Koichi ITO koic
1
730
Oxcを導入して開発体験が向上した話
Avatar for Yuji Yamaguchi yug1224
4
310
Signal Forms: Details & Live Coding @enterJS 2026 in Mannheim
Avatar for Manfred Steyer manfredsteyer
PRO
0
110
運用エージェントは "作る" から "育てる" へ - 記憶と自己進化の3層設計パターン / self-evolving-agents-three-layer-agent-design
Avatar for geeawa gawa
12
3.6k
IBM Bobを活用したレガシーアプリの最新化
Avatar for Akira Onishi (IBM) oniak3ibm
PRO
1
190
AIで効率化できた業務・日常
Avatar for Ochtum ochtum
0
130
Spec Driven Development | AI Summit Lisbon
Avatar for Daniel Sogl danielsogl
PRO
0
180
New "Type" system on PicoRuby
Avatar for pocke pocke
1
850
PHPで使える日時の表現と、その知り方 #frontend_phpcon_do
Avatar for hideki kinjyo o0h
PRO
0
230

Featured

See All Featured
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
Avatar for Stéphanie Walter stephaniewalter
287
14k
Producing Creativity
Avatar for Steve Smith orderedlist
PRO
348
40k
Digital Ethics as a Driver of Design Innovation
Avatar for Per Axbom axbom
PRO
1
310
Exploring anti-patterns in Rails
Avatar for Elle Meredith aemeredith
3
400
We Have a Design System, Now What?
Avatar for Morgane Peng morganepeng
55
8.2k
Six Lessons from altMBA
Avatar for Skipper Chong Warson skipperchong
29
4.3k
Building Applications with DynamoDB
Avatar for Matt Wood mza
96
7.1k
Lightning Talk: Beautiful Slides for Beginners
Avatar for Ines Montani inesmontani
PRO
2
570
Applied NLP in the Age of Generative AI
Avatar for Ines Montani inesmontani
PRO
4
2.3k
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
Avatar for soudai sone soudai
PRO
65
55k
Fantastic passwords and where to find them - at NoRuKo
Avatar for Phil Nash philnash
52
3.7k
Practical Tips for Bootstrapping Information Extraction Pipelines
Avatar for Matthew Honnibal honnibal
25
2k

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