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
700
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
240
TDD in JavaScript
Avatar for Alexander Beletsky alexbeletsky
4
860
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
460
Likeastore
Avatar for Alexander Beletsky alexbeletsky
3
150
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
630

Other Decks in Programming

See All in Programming
ソフトウェア設計の結合バランス #phperkaigi
Avatar for Takuma Kajikawa kajitack
0
510
AI時代になぜ書くのか
Avatar for Mutz mutsumix
0
410
How We Practice Exploratory Testing in Iterative Development( #scrumniigata ) / 反復開発の中で、探索的テストをどう実施しているか
Avatar for teyamagu teyamagu
PRO
3
850
AI Agent と正しく分析するための環境作り
Avatar for yosh_yumyum yoshyum
2
520
PicoRuby for IoT: Connecting to the Cloud with MQTT
Avatar for Y_uuu yuuu
2
780
Hive Metastoreを通して学ぶIceberg REST Catalog ― 仕様から実装まで
Avatar for okumin okumin
0
140
サーバーレスで作る、動画データ管理基盤
Avatar for Keigo Ibaraki oyasumipants
0
210
Spec Driven Development | AI Summit Vilnius
Avatar for Daniel Sogl danielsogl
PRO
1
160
クラウドネイティブなエンジニアに向ける Raycastの魅力と実際の活用事例
Avatar for Nealle nealle
2
260
なぜあなたのコードには「コシ」がないのか？〜AI時代に問う、最後まで美味しい設計と戦略〜 #phpconkagawa / phpconkagawa2026
Avatar for shogogg shogogg
0
210
「OSSがあるなら自作するな」は AI時代も正しいか ── Build vs Adopt の新しい判断基準
Avatar for Kumo Ishikawa kumorn5s
7
2.7k
Agentic AI & UI: Arcitecture, HITL, Emerging Standards
Avatar for Manfred Steyer manfredsteyer
PRO
0
110

Featured

See All Featured
Automating Front-end Workflow
Avatar for Addy Osmani addyosmani
1370
200k
WCS-LA-2024
Avatar for Leonardo Collado-Torres lcolladotor
0
590
Scaling GitHub
Avatar for Zach Holman holman
464
140k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
Avatar for mongodb mongodb
49
9.9k
What Being in a Rock Band Can Teach Us About Real World SEO
Avatar for Ade Holder 427marketing
0
230
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
Avatar for panda_program panda_program
122
21k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
Avatar for Morgane Peng morganepeng
133
19k
Jamie Indigo - Trashchat’s Guide to Black Boxes: Technical SEO Tactics for LLMs
Avatar for Tech SEO Connect techseoconnect
PRO
0
140
ピンチをチャンスに：未来をつくるプロダクトロードマップ #pmconf2020
Avatar for Aki / @LoveIdahoBurger aki_iinuma
128
55k
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
Avatar for Liv Day livdayseo
0
120
The Director’s Chair: Orchestrating AI for Truly Effective Learning
Avatar for Mike Taylor tmiket
1
170
4 Signs Your Business is Dying
Avatar for Josh Pigford shpigford
187
22k

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