Mon premier blog

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

In my previous post I gave an example of the benefits of fixing a bug by first writing a test. Jan 1, 2012 - For example, I use one metaphor when describing the business value of TDD with the organization's leadership, and another when describing the personal value to the members of the development team. May 15, 2014 - DHH appears to have a dim view on TDD practicing developers; whom he generalises write simple unit tests having 100% code coverage, use many mocks, but test nothing real. Jun 15, 2008 - Naresh, meanwhile, is on a mission to pair program with the world to understand how different people approach Test-Driven Development, with an example problem that he uses with everyone. I've dubbed it David gives an example of why unit tests aren't valuable because they didn't catch a BaseCamp bug to do with attachments (hint: the issue isn't to do with unit testing per se, but having only one style of tests). The process can be explained in five simple steps: 1. May 13, 2014 - If you've somehow managed to miss the keynote, blog post and subsequent shitstorm about it, David Heinemeier Hansson (dhh), creator of ruby on rails, has recently come out and declared test-driven development (TDD) dead. Even if my example had actually shown such a test, bugfixing isn't the archetypal TDD scenario. 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. Apr 28, 2014 - The idea behind TDD can be stated by improvising this phrase: 'lead by an example' to 'code by an example'. 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. This involves writing all your tests up front before any development has taken place.