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

Test Driven Development (A Short Introduction)

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →
Avatar for John Chandler John Chandler
April 08, 2011
Programming
0
13

Test Driven Development (A Short Introduction)

Internal company presentation, 2011.

Avatar for John Chandler

John Chandler

April 08, 2011
Tweet

More Decks by John Chandler

See All by John Chandler
Everything I've Learnt from Russel Winder's Talks, in 5 Minutes (A Tribute)
Avatar for John Chandler metaljoe
0
13
Snowboarding Saved My Software Career
Avatar for John Chandler metaljoe
0
11
Neurodiversity in Tech
Avatar for John Chandler metaljoe
0
55
Neurodiversity Lightning Talk
Avatar for John Chandler metaljoe
0
14
Tackling a Legacy Codebase with (Micro)Services
Avatar for John Chandler metaljoe
0
11
Regular Expressions
Avatar for John Chandler metaljoe
0
16
Testing Workshop - Part 1 (PyConUK 2011)
Avatar for John Chandler metaljoe
0
19
Testing Workshop - Part 2 (PyConUK 2011)
Avatar for John Chandler metaljoe
0
14
Python, DOT, and Visualising Legacy Code The Lazy Way
Avatar for John Chandler metaljoe
0
20

Other Decks in Programming

See All in Programming
Rust 製のコードエディタ “Zed” を使ってみた
Avatar for NearMeの技術発表資料です nearme_tech
PRO
0
180
Data-Centric Kaggle
Avatar for ねぼすけAI isax1015
2
770
高速開発のためのコード整理術
Avatar for sutetotanuki sutetotanuki
1
400
Implementation Patterns
Avatar for Denys Poltorak denyspoltorak
0
290
Architectural Extensions
Avatar for Denys Poltorak denyspoltorak
0
290
ぼくの開発環境2026
Avatar for yuzneri yuzneri
0
220
疑似コードによるプロンプト記述、どのくらい正確に実行される？
Avatar for kokuyouwind kokuyouwind
0
390
The Past, Present, and Future of Enterprise Java
Avatar for ivargrimstad ivargrimstad
0
570
組織で育むオブザーバビリティ
Avatar for ryotaro kobayashi ryota_hnk
0
170
フロントエンド開発の勘所 -複数事業を経験して見えた判断軸の違い-
Avatar for Yoichiro Kubo heimusu
7
2.8k
AI Schema Enrichment for your Oracle AI Database
Avatar for thatjeffsmith thatjeffsmith
0
280
AIによる高速開発をどう制御するか？ ガードレール設置で開発速度と品質を両立させたチームの事例
Avatar for tonkotsuboy_com tonkotsuboy_com
7
2.3k

Featured

See All Featured
The Anti-SEO Checklist Checklist. Pubcon Cyber Week
Avatar for Ryan Jones ryanjones
0
65
Building Experiences: Design Systems, User Experience, and Full Site Editing
Avatar for Michelle Schulp Hunt marktimemedia
0
410
Gemini Prompt Engineering: Practical Techniques for Tangible AI Outcomes
Avatar for Mfonobong Umondia mfonobong
2
280
Designing Experiences People Love
Avatar for Jonathan Moore moore
144
24k
Navigating the moral maze — ethical principles for Al-driven product design
Avatar for Skipper Chong Warson skipperchong
2
240
A designer walks into a library…
Avatar for Paul Jervis Heath pauljervisheath
210
24k
Bridging the Design Gap: How Collaborative Modelling removes blockers to flow between stakeholders and teams @FastFlow conf
Avatar for Kenny Baas-Schwegler baasie
0
450
Side Projects
Avatar for Sacha Greif sachag
455
43k
Have SEOs Ruined the Internet? - User Awareness of SEO in 2025
Avatar for Akash Hashmi akashhashmi
0
270
The World Runs on Bad Software
Avatar for Brandon Keepers bkeepers
PRO
72
12k
ラッコキーワード サービス紹介資料
Avatar for ラッコ株式会社 rakko
1
2.3M
It's Worth the Effort
Avatar for 3n 3n
188
29k

Transcript

  1. Test Driven Development (a short introduction) (C) John Chandler 2011

  2. Perfect Code? First Time? Every Time? (yeah right)

  3. Confidence Through Tests Manual Tests = Error Prone Automated Tests

    = Repeatable

  4. Writing Tests After the Code Is Useful

  5. Writing Tests Before the Code Helps us...

  6. Think about What before we decide How

  7. Write code that is easy to test

  8. Write small units of code at a time

  9. Ensure all code has test coverage

  10. Know when to stop writing code

  11. First we write a test that fails

  12. Then we write code to make the test pass

  13. Did we break anything?

  14. Are we more confident?

  15. Refactor if necessary Refactor with confidence

  16. Then repeat until done

  17. What else?

  18. Fail Fast Early Feedback

  19. Easier to learn unfamiliar code

  20. Easier to change unfamiliar code

  21. Supplementary code documentation

  22. Give confidence to Others

  23. Continuous Integration

  24. Now go write tests!