Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to write good tests?

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest. →
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
860
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
450
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.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
620

Other Decks in Programming

See All in Programming
atmaCup #23でAIコーディングを活用した話
Avatar for ML_Bear ml_bear
4
710
Rで始めるML・LLM活用入門
Avatar for wakama1994 wakamatsu_takumu
0
120
AI駆動開発の本音 〜Claude Code並列開発で見えたエンジニアの新しい役割〜
Avatar for hisuzuya hisuzuya
3
430
社内規程RAGの精度を73.3% → 100%に改善した話
Avatar for oharu121 oharu121
12
6.1k
モジュラモノリスにおける境界をGoのinternalパッケージで守る
Avatar for magavel magavel
0
3.3k
Claude Codeと2つの巻き戻し戦略 / Two Rewind Strategies with Claude Code
Avatar for 果物リン fruitriin
0
200
今更考える「単一責任原則」 / Thinking about the Single Responsibility Principle
Avatar for philomagi tooppoo
3
1.2k
Event Storming
Avatar for Henning Schwentner hschwentner
3
1.3k
Rubyと楽しいをつくる / Creating joy with Ruby
Avatar for chobishiba chobishiba
0
200
AIエージェントのキホンから学ぶ「エージェンティックコーディング」実践入門
Avatar for Masahiro Nishimi masahiro_nishimi
7
1.2k
RAGでハマりがちな"Excelの罠"を、データの構造化で突破する
Avatar for harumi harumiweb
8
2.1k
Beyond the Basics: Signal Forms
Avatar for Manfred Steyer manfredsteyer
PRO
0
110

Featured

See All Featured
Lessons Learnt from Crawling 1000+ Websites
Avatar for Charles Meaden charlesmeaden
PRO
1
1.1k
Building Adaptive Systems
Avatar for Chris Keathley keathley
44
2.9k
A better future with KSS
Avatar for Kyle Neath kneath
240
18k
Fight the Zombie Pattern Library - RWD Summit 2016
Avatar for Marcelo Somers marcelosomers
234
17k
Agile Actions for Facilitating Distributed Teams - ADO2019
Avatar for Mark Kilby mkilby
0
140
ReactJS: Keep Simple. Everything can be a component!
Avatar for Pedro Nauck pedronauck
666
130k
The Illustrated Children's Guide to Kubernetes
Avatar for Chris Short chrisshort
51
52k
The Success of Rails: Ensuring Growth for the Next 100 Years
Avatar for Eileen M. Uchitelle eileencodes
47
8k
Git: the NoSQL Database
Avatar for Brandon Keepers bkeepers
PRO
432
66k
My Coaching Mixtape
Avatar for mlcsv mlcsv
0
63
Optimizing for Happiness
Avatar for Tom Preston-Werner mojombo
379
71k
End of SEO as We Know It (SMX Advanced Version)
Avatar for Michael King ipullrank
3
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