Test-driven development by example Kent Beck
Publisher: Addison-Wesley Professional

Dec 9, 2005 - Benefits of Test-Driven Development: Kent Beck, in the preface to this book mentions Ron Jeffries' pithy phrase, 'Clean code that works', and suggests that this is the goal of Test-Driven Development. It's an excellent talk, and I would highly As a minimal counter-example, TDD doesn't stop you using terrible names for things. Now, it's been several years since I learned and practised TDD. Here, we dive into a real-life example of using TDD to develop production Apex code for Salesforce CRM. The team establishes a backlog of prioritized user stories based on the functional and architectural requirements. Feb 11, 2013 - Test driven development is a development process that is exactly what it sounds like, we develop our applications driven by a number of different tests. I recently recorded how I used TDD to solve a sample problem. Mar 5, 2012 - In an earlier blog, we examined a simple example of Test Driven Development (TDD). In order to demonstrate code contracts, I'm going to return to the Category class that I used as an example in my blog post Advanced Test-Driven Development. Jul 31, 2012 - This is my third time read. This involves writing all your tests up front before any development has taken place. Dec 11, 2013 - An example of TDD with ATDD and BDD attributes (or TDD/ATDD/BDD run through a blender just a bit) I. Jun 19, 2013 - Instant RSpec Test-Driven Development How-to is filled with examples of actual code accompanied by explanations and covers general Ruby, Rails, and RSpec use cases plus a few of the more advanced topics. Mar 28, 2011 - The last installment of our series introduced Test-First Programming and briefly discussed its refinements: Test-Driven Development and Behavior-Driven Development. Mar 7, 2014 - I'm going to weigh in on that debate. May 9, 2014 - In a recent keynote at RailsConf called Writing Software*, David Heinemeier Hansson argues that test-driven development (TDD) can harm the clarity of our code, and that clarity is the key thing we should be aiming for when writing software. When I read it first time, I didn't know much of TDD and wanted to grasp its concept.