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
iOS 26にアップデートすると実機でのHot Reloadができない？
Avatar for Aoi Umigishi umigishiaoi
0
130
Railsアプリケーションと パフォーマンスチューニング ー 秒間5万リクエストの モバイルオーダーシステムを支える事例 ー Rubyセミナー 大阪
Avatar for Hayato OKUMOTO falcon8823
5
1.1k
10 Costly Database Performance Mistakes (And How To Fix Them)
Avatar for Andrew Atkinson andyatkinson
0
440
Hack Claude Code with Claude Code
Avatar for Akihiro Okuno choplin
5
2.3k
Goで作る、開発・CI環境
Avatar for Shinpei Mine sin392
0
240
初学者でも今すぐできる、Claude Codeの生産性を10倍上げるTips
Avatar for Oikon s4yuba
16
12k
MCPを使ってイベントソーシングのAIコーディングを効率化する / Streamlining Event Sourcing AI Coding with MCP
Avatar for Tomohisa Takaoka tomohisa
0
120
Rubyでやりたい駆動開発 / Ruby driven development
Avatar for chobishiba chobishiba
1
740
AI時代の『改訂新版 良いコード／悪いコードで学ぶ設計入門』 / ai-good-code-bad-code
Avatar for MinoDriven minodriven
20
8.2k
オンコール⼊⾨〜ページャーが鳴る前に、あなたが備えられること〜 / Before The Pager Rings
Avatar for Yuuki Takahashi yktakaha4
0
150
たった 1 枚の PHP ファイルで実装する MCP サーバ / MCP Server with Vanilla PHP
Avatar for Shohei Okada okashoi
1
270
XP, Testing and ninja testing
Avatar for seki at druby.org m_seki
3
250

Featured

See All Featured
What's in a price? How to price your products and services
Avatar for Michael Herold michaelherold
246
12k
Rebuilding a faster, lazier Slack
Avatar for samanthasiow samanthasiow
83
9.1k
Facilitating Awesome Meetings
Avatar for Lara Hogan lara
54
6.4k
Raft: Consensus for Rubyists
Avatar for Patrick Van Stee vanstee
140
7k
No one is an island. Learnings from fostering a developers community.
Avatar for Antonio thoeni
21
3.4k
Done Done
Avatar for chrislema chrislema
184
16k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
Avatar for Stéphanie Walter stephaniewalter
281
13k
4 Signs Your Business is Dying
Avatar for Josh Pigford shpigford
184
22k
Speed Design
Avatar for Sergey Chernyshev sergeychernyshev
32
1k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
Avatar for Rebecca Miller-Webster rmw
34
3.1k
Fight the Zombie Pattern Library - RWD Summit 2016
Avatar for Marcelo Somers marcelosomers
233
17k
Intergalactic Javascript Robots from Outer Space
Avatar for Vicent Martí tanoku
271
27k

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