Skip to content
0:00 / 0:00

#tdd#testdrivendevelopment#continuousdelivery

When Test Driven Development Goes Wrong

Modern Software Engineering

265K subscribers • 10 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Dave Farley, pioneer of Continuous Delivery

Intermediate. Assumes working knowledge.

75K views5 years ago2 recommendations

Tools and practiceSoftware designTestingDesign patternsRefactoring and legacy code

Dave Farley explains five common pitfalls of Test Driven Development and how to use TDD effectively to improve software design.

Test Driven Development is one of the best ways that we have to amplify our talent as software developers, maybe software engineers. This Software Engineering practice is one of the best ways to improve the quality of your code, but it is difficult to do it well, and it often goes wrong. The interesting thing is that when it goes wrong, it may be at its most valuable. TDD is a cornerstone of Continuous Delivery, BDD and DevOps. Using it to give us valuable, efficient feedback on the quality of our designs is at the heart of its value but is often missed by people who are new to it. Dave explores these ideas with some real code examples to demonstrate the value of TDD. In this episode, Dave Farley explains 5 common ways that TDD goes wrong, how to fix them, and what we can learn from them. Some of the ideas in this video were inspired by this blog post: ➡️ web.archive.org/web/20100105084725/http://blog.james-carr.or… ------------------------------------------------------------------------------------- 🎓 CD TRAINING COURSES 🎓 If you want to learn Continuous Delivery and DevOps skills, check out Dave Farley's courses ➡️ bit.ly/DFTraining 📚 BOOKS: 📖 Dave’s NEW BOOK "Modern Software Engineering" is now available on Amazon ➡️ amzn.to/3DwdwT3 In this book, Dave brings together his ideas and proven techniques to describe a durable, coherent and foundational approach to effective software development, for programmers, managers and technical leads, at all levels of experience. 📖 "Continuous Delivery Pipelines" by Dave Farley paperback ➡️ amzn.to/3gIULlA ebook version ➡️ leanpub.com/cd-pipelines 📖 The original "Continuous Delivery" book by Dave Farley and Jez Humble ➡️ amzn.to/2WxRYmx 📧 JOIN CD MAIL LIST 📧 Keep up to date with the latest discussions, free "How To..." guides, events and online courses. ➡️ bit.ly/MailListCD ------------------------------------------------------------------------------------- Dave Farley's Blog ➡️ bit.ly/DaveFWebBlog Dave Farley on Twitter ➡️ bit.ly/DaveFTwitter Dave Farley on LinkedIn ➡️ bit.ly/DaveF-LI

Why it's here

2 people recommend this

What people say. Recommended as a great resource for identifying bad testing patterns and understanding how to write meaningful tests.

u/the-computer-guySoftware Engineerin r/ExperiencedDevs • Recommends

On “Resources with examples of bad and "fake" tests?”

link to this video

u/Ratslayer1in r/ExperiencedDevs • Recommends

On “Resources with examples of bad and "fake" tests?”

As none of the top comments seem to answer your actual question of names of common ways tests go wrong, here is a youtube video with several examples: link to this video