Kent Beck – CS@Worcester https://cs.worcester.edu Worcester State University Computer Science Department Thu, 20 Oct 2016 19:59:45 +0000 en-US hourly 1 https://wordpress.org/?v=6.9 236835116 Lessons to Learn from Kent Beck the father of TDD http://www.tylerlundstrom.com/lessons-to-learn-from-kent-beck-the-father-of-tdd/ Thu, 20 Oct 2016 19:59:45 +0000 http://www.tylerlundstrom.com/?p=184 Continue reading "Lessons to Learn from Kent Beck the father of TDD"]]> In a podcast I listened to earlier this week from PythonTesting, Test & Code podcast, I was able to hear from the “father” of TDD himself Kent Beck. In this podcast, the host Brian took snippets from a Software Engineering radio podcast (Episode 167) that, what he thought, would have the most impact on the listener.

These are the 5 things Brian decided to look at:

  1. You’re tests should tell a story.

  2. Be careful of DRY, inheritance, and other software development practices that might get in the way of keeping your tests easy to understand.

  3. All test should help differentiate good programs from bad programs and not be redundant.

  4. Test at multiple levels and multiple scales where it makes sense.

  5. Differentiating between TDD, BDD, ATDD, etc. isn’t as important as testing your software to learn about it. Who cares what you call it.

One interesting thing I noted from this was point number 2. Being careful of writing test that align with common software design practices. This kind of went hand-in-hand with point 1 where he says your tests should tell a story. Each individual test should tell the person reading it, what was being accomplished at that given point. For example if you try to use the Don’t Repeat Yourself (DRY) philosophy then you won’t be able to see that story as well in your tests because you’ve tried consolidating the repeats.

From the blog CS@Worcester – Tyler Lundstrom by CS@Worcester – Tyler Lundstrom and used with permission of the author. All other rights reserved by the author.

]]> 4512