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

3 Steps Every Test Should Take

Matheus Richard
May 27, 2021
Programming
0
64

3 Steps Every Test Should Take

Matheus Richard

May 27, 2021
Tweet

More Decks by Matheus Richard

See All by Matheus Richard
The Fast Lane: Asynchronous Rails
matheusrich
0
27
Build in Private
matheusrich
0
53
Start TDDing in 5 minutes
matheusrich
0
88
Taming God Objects: easy, incremental and secure
matheusrich
1
76
Stimulus 2.0-alpha - What's new?
matheusrich
0
47
BEM - A simple CSS methodology
matheusrich
0
44
De Repente 7
matheusrich
0
11

Other Decks in Programming

See All in Programming
GitHub Actionsのキャッシュと手を挙げることの大切さとそれに必要なこと
satoshi256kbyte
5
430
Content Security Policy入門 セキュリティ設定と 違反レポートのはじめ方 / Introduction to Content Security Policy Getting Started with Security Configuration and Violation Reporting
uskey512
1
520
Amazon Bedrock Agentsを用いてアプリ開発してみた！
har1101
0
330
Laravel や Symfony で手っ取り早く
OpenAPI のドキュメントを作成する
azuki
1
110
タクシーアプリ『GO』のリアルタイムデータ分析基盤における機械学習サービスの活用
mot_techtalk
4
1.4k
詳細解説！ ArrayListの仕組みと実装
yujisoftware
0
580
Streams APIとTCPフロー制御 / Web Streams API and TCP flow control
tasshi
2
350
OnlineTestConf: Test Automation Friend or Foe
maaretp
0
110
弊社の「意識ﾁｮｯﾄ低いアーキテクチャ」10選
texmeijin
5
24k
EventSourcingの理想と現実
wenas
6
2.3k
Why Jakarta EE Matters to Spring - and Vice Versa
ivargrimstad
0
1k
OSSで起業してもうすぐ10年 / Open Source Conference 2024 Shimane
furukawayasuto
0
100

Featured

See All Featured
Gamification - CAS2011
davidbonilla
80
5k
Practical Orchestrator
shlominoach
186
10k
What's new in Ruby 2.0
geeforr
343
31k
Typedesign – Prime Four
hannesfritz
40
2.4k
Rails Girls Zürich Keynote
gr2m
94
13k
Fontdeck: Realign not Redesign
paulrobertlloyd
82
5.2k
Fireside Chat
paigeccino
34
3k
ピンチをチャンスに：未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
109
49k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
126
18k
Visualization
eitanlees
145
15k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
169
50k
Being A Developer After 40
akosma
86
590k

Transcript

  1. 3 Steps Every Test Should Take

  2. About me Matheus Richard

  3. This is a ⚡lightning talk⚡, so I’m gonna go FAST

    󰝊💨

  4. 🧪 Tests

  5. 😄 Tests are good! They make us more productive. Right?

  6. ❌ WRONG!

  7. ✔Good tests are good

  8. 🐢 Poorly written tests slow us down!

  9. Developer happiness-meter: 🙁 🐌 Slow tests

  10. Developer happiness-meter: 😞 🤔 Confusing tests 🐌 Slow tests

  11. 󰣽 Flaky tests Developer happiness-meter: 😠 🤔 Confusing tests 🐌

    Slow tests

  12. 󰣽 Flaky tests Developer happiness-meter: 🤬 🤔 Confusing tests 📦

    Brittle tests 🐌 Slow tests

  13. 🐌 Slow tests 󰣽 Flaky tests 📦 Brittle tests 🤔

    Confusing tests

  14. Good tests tell a story

  15. The story has 4 acts

  16. 📝 1. Setup

  17. 📝 1. Setup Create objects Define function inputs

  18. 📝 1. Setup 🏋 2. Exercise

  19. 📝 1. Setup 🏋 2. Exercise Calling methods Saving objects

    to DB

  20. 📝 1. Setup 🏋 2. Exercise 󰡷 3. Verify

  21. 📝 1. Setup 🏋 2. Exercise 󰡷 3. Verify Check

    if the output is the expected

  22. 📝 1. Setup 󰡷 3. Verify 🏋 2. Exercise 💥

    4. Teardown

  23. 📝 1. Setup 󰡷 3. Verify 🏋 2. Exercise 💥

    4. Teardown Undo changes Release memory Restore DB

  24. 📝 1. Setup 🏋 2. Exercise 󰡷 3. Verify 💥

    4. Teardown You’re welcome!

  25. 📝 1. Setup 󰡷 3. Verify 🏋 2. Exercise

  26. 📝 1. Arrange 󰡷 3. Assert 🏋 2. Act aka

  27. 📝 1. Given 󰡷 3. Then 🏋 2. When aka

  28. None
  29. None
  30. None

  31. 🤨 Why is this good?

  32. Consistency

  33. None
  34. None
  35. None
  36. None

  37. E X E R C I S E

  38. Tests are self-contained. No mystery guests here

  39. None

  40. 1. Verify Developer confusion-meter: 🤔❓

  41. 1. Verify 2. Exercise + Setup Developer confusion-meter: 🥴⁉

  42. 1. Verify 2. Exercise + Setup? 3. Verify Developer confusion-meter:

    😵

  43. Developer confusion-meter: 😵

  44. Developer happiness-meter: 🥰

  45. SPACE IS IMPORTANT Developer happiness-meter: 🥰

  46. Developer happiness-meter: 😐

  47. Developer happiness-meter: 🥰

  48. Good tests have 4 3 steps

  49. 📝 1. Setup

  50. 📝 1. Setup 🏋 2. Exercise

  51. 📝 1. Setup 󰡷 3. Verify 🏋 2. Exercise

  52. We need not only tests, but good tests!

  53. We want good code and tests are code too!

  54. That’s it Feel free to ask any question