Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
How to write good tests?
Search
Alexander Beletsky
April 12, 2013
Programming
370
2
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
How to write good tests?
Small talk that I gave to @debitoor guys about practices of writing tests.
Alexander Beletsky
April 12, 2013
More Decks by Alexander Beletsky
See All by Alexander Beletsky
Snapshot Testing: Going beyond UI
alexbeletsky
1
730
Tech Culture in Startups
alexbeletsky
0
280
TDD in JavaScript
alexbeletsky
4
880
This is Node.js
alexbeletsky
10
490
Likeastore
alexbeletsky
3
200
PaaS in your pocker with Dokku
alexbeletsky
7
2.7k
Building Single Page Applications
alexbeletsky
9
5.5k
.NET developer in JavaScript world
alexbeletsky
1
2.9k
Dynamic web development with Oak
alexbeletsky
1
680
Other Decks in Programming
See All in Programming
AIが生成したコードは読むべきか?抽象化設計とコードの品質保証 / abstraction-design-and-quality
minodriven
16
8.6k
Herb in Rails 8.2: Your ERB views, now HTML-aware @ Kaigi on Rails 2026, Tokyo, Japan
marcoroth
2
410
Crash Auto Pipelines
veronikapj
1
350
Inertia Rails: The One-Person Framework with React & Friends
skryukov
0
380
Optunaを作ったときにやりたかったこと、その後 (2026/10/16, Optuna Meetup #3)
iwiwi
4
1.5k
作れる、でも消せるか?──安全に「枯らして消す」機能削除術 / Drain, Then Delete
chobishiba
3
1.4k
Getting Started with Vibe Coding
miccheng
0
180
Augmenting AI with the Power of Jakarta EE
ivargrimstad
0
580
Seven New Principles of Software Engineering
yegor256
0
440
當我們開始不讀 Code - AI Agent 時代,Code Review 與 Clean Code 還剩下什麼?
jame2408
1
360
Performance Optimization With LLMs
xleitix
0
240
作れるエンジニアから、価値を届けるエンジニアへ
ryunakayama
1
180
Featured
See All Featured
Done Done
chrislema
187
17k
How STYLIGHT went responsive
nonsquared
100
6.4k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
133
20k
30 Presentation Tips
portentint
PRO
1
460
Ten Tips & Tricks for a 🌱 transition
stuffmc
1
280
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
620
Groundhog Day: Seeking Process in Gaming for Health
codingconduct
0
460
Build your cross-platform service in a week with App Engine
jlugia
234
19k
HU Berlin: Industrial-Strength Natural Language Processing with spaCy and Prodigy
inesmontani
PRO
0
800
Effective software design: The role of men in debugging patriarchy in IT @ Voxxed Days AMS
baasie
1
600
What the history of the web can teach us about the future of AI
inesmontani
PRO
2
790
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
28
3.7k
Transcript
How to write good tests?
Honestly, I don’t know
But, there are properties of good tests…
… are written before code
… are running very fast
… are helping to find regressions
Writing unit tests is not about code verification
… it’s about code quality and design
Think different Think TDD
Could TDD be applied to everything?
In short, yes code, requirements, ui
Should TDD be applied to everything?
Probably, no simple tasks, prototypes
There are few techniques of writing tests
Classic school Kent Beck, 90’s Inside-Out design Focusing on logic
(algorithms)
London school Jason Gorman, 00’s Outside-In design Focusing on collaboration
Mocks
What about integration tests?
They are slow, hard to write, hard to setup… but
… they usually caught most nasty bugs.
None
Maintaining test driven cycle
None
Acceptance test (PO communication) API (integration) tests Utils (units) tests
Thanks, @alexbeletsky