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

How to write good tests?

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →
Avatar for Alexander Beletsky Alexander Beletsky
April 12, 2013
Programming
360
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
720
Tech Culture in Startups
Avatar for Alexander Beletsky alexbeletsky
0
260
TDD in JavaScript
Avatar for Alexander Beletsky alexbeletsky
4
870
This is Node.js
Avatar for Alexander Beletsky alexbeletsky
10
480
Likeastore
Avatar for Alexander Beletsky alexbeletsky
3
180
PaaS in your pocker with Dokku
Avatar for Alexander Beletsky alexbeletsky
7
2.7k
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
660

Other Decks in Programming

See All in Programming
AIエージェント時代のコードレビューを設計する
Avatar for nogu nogu66
5
1.2k
GKE アップグレード前に知っておきたい Blue/Green と PDB の関係
Avatar for Sota Takaki stkk
0
120
tsc.rip を支える技術 / Kyoto.なんか #8
Avatar for Susisu susisu
0
4.1k
DynamoDBの基礎を振り返りながらベクトル検索機能を理解する
Avatar for 村上優稀 musan
3
260
Pythonの実行はどこまで賢くなったのか？ CPythonとPyPyから見る最適化のしくみ
Avatar for curekoshimizu curekoshimizu
4
2.4k
LLMは4年分のCompose移行を再現できるのか？実プロダクト279件のXMLで探る自動化の境界線
Avatar for makun makun
0
250
源内ハンズオン概要編
Avatar for Hideyuki Nagata hideg
0
240
【QA Test Talk Vol.8】AI-DLC による Whole Team Approach の加速
Avatar for PKSHA Technology（パークシャテクノロジー） pkshadeck
PRO
0
270
Webエンジニアなのにブラウザの仕組みがわからないので、Pythonで自作してみた
Avatar for Tatsuki tatsuki12
4
1.6k
自分的「カンファレンスの楽しみ方」
Avatar for syumai syumai
0
170
書籍「プロフェッショナルAI駆動開発」紹介スライド
Avatar for Juntaro Matsumoto juntaromatsumoto
0
870
My Marp Sample
Avatar for Shota Inoue sinoue0108
0
140

Featured

See All Featured
Hiding What from Whom? A Critical Review of the History of Programming languages for Music
Avatar for Tomoya Matsuura tomoyanonymous
3
1.2k
Understanding Cognitive Biases in Performance Measurement
Avatar for Philip Tellis bluesmoon
32
3k
[RailsConf 2023] Rails as a piece of cake
Avatar for Vladimir Dementyev palkan
59
6.9k
Marketing to machines
Avatar for Jono Alderson jonoalderson
1
5.7k
Evolving SEO for Evolving Search Engines
Avatar for Ryan Jones ryanjones
0
270
KATA
Avatar for Megan Lloyd mclloyd
PRO
35
15k
Kristin Tynski - Automating Marketing Tasks With AI
Avatar for Tech SEO Connect techseoconnect
PRO
0
490
Heart Work Chapter 1 - Part 1
Avatar for Lake Fama lfama
PRO
8
36k
The Success of Rails: Ensuring Growth for the Next 100 Years
Avatar for Eileen M. Uchitelle eileencodes
47
8.3k
Designing for humans not robots
Avatar for Tammie Lister tammielis
254
26k
sira's awesome portfolio website redesign presentation
Avatar for ElsiraPls elsirapls
0
380
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
Avatar for Kevin Liebholz kevinliebholz
37
6.6k

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