ATDD
DIVERS
+ DE 2 ANS
Le 24/01/2020 à 05h45
1010 vues
Question d'origine :
Bonjour,
Qui a inventé l'ATDD (Acceptance Test Driven Development) ? Et quand ?
Je n'arrive pas à trouver ces informations...
Merci d'avance !
Zozolat
Réponse du Guichet
gds_et
- Département : Équipe du Guichet du Savoir
Le 27/01/2020 à 10h28
Bonjour,
D’après les sources que nous avons pu consulter, il semble que l’une des mentions les plus anciennes de l’ATDD se trouve dans l’ouvrage de Kent Beck paru en 2003 : Test-Driven Development. On peut difficilement attribuer la paternité de cette méthodologie à un inventeur unique ; elle s’inscrit dans une lignée comportant de multiples variantes.
« ATDD Lineage
A Chinese proverb says, « there are many paths to the top of the mountain, but the view is always the same. » And many of the paths share the same trail for portions of the journey. Althoughacceptance testing has been around for a long time , it was reinvigorated by extreme programming. Its manifestations include ATDD as described in this book, example-driven development (EDD) by Brian Marick, behavior-driven development (BDD) by Dan North, story test-driven development (SDD) by Joshua Kerievsky of Industrial Logic, domain-driven design (DDD) by Eric Evans, and executable acceptance test-driven development (EATDD) . All these share the common goal of producing high-quality software. They aid developers and testers in understanding the customer’s needs prior to implementation and customers being able to converse in their own domain language.
Many aspects are shared among the different approaches. ATDD in this book encompasses aspects of these other approaches. I’ve documented the parts that come specifically from the other driven developments (DDs), including Brian Marick’s examples, Eric Evan’s ubiquitous language, and Dan North’s given-when-then template. The most visible differences are that the tests here are presented in table format rather than in a more textual format, such as BDD’s Cucumber language, and they concentrate on functionality instead of the user interface. This books’s version of ATDD matches closely that described byLasse Koskela and Gojko Adzic and follows the testing recommendations of Jim Coplien .
One of the most well-known DDs istest-driven development (TDD) by Kent Beck . TDD encompasses the developer’s domain and tests the units or modules that comprise a system. TDD has the same quality goal as ATDD. The two interrelate because the acceptance tests can form a context in which to derive the tests for the units. TDD helps creates the best design for an application. A TDD design issue would be assigning responsibilities to particular modules or classes to pass all or part of an acceptance test. »
Source : Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration, Ken Pugh
« Origins
• 2003: Kent Beck briefly mentions ATDD in the book “Test Driven Development: By Example” but dismisses it as impractical
• 2003 to 2004: driven by the popularity of Fit/FitNesse ATDD becomes accepted practice in spite of Beck’s objections »
Source : agilealliance.org
« In his recent book “Test-Driven Development”, Kent Beck describes briefly the concept of “ Acceptance-Test Driven Development”, and is broadly sceptical to whether it will work. »
Source : Andersson J., Bache G., Sutton P. (2003) XP with Acceptance-Test Driven Development: A Rewrite Project for a Resource Optimization System. In: Marchesi M., Succi G. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2003. Lecture Notes in Computer Science, vol 2675. Springer, Berlin, Heidelberg
Bonne journée.
D’après les sources que nous avons pu consulter, il semble que l’une des mentions les plus anciennes de l’ATDD se trouve dans l’ouvrage de Kent Beck paru en 2003 : Test-Driven Development. On peut difficilement attribuer la paternité de cette méthodologie à un inventeur unique ; elle s’inscrit dans une lignée comportant de multiples variantes.
« ATDD Lineage
A Chinese proverb says, « there are many paths to the top of the mountain, but the view is always the same. » And many of the paths share the same trail for portions of the journey. Although
Many aspects are shared among the different approaches. ATDD in this book encompasses aspects of these other approaches. I’ve documented the parts that come specifically from the other driven developments (DDs), including Brian Marick’s examples, Eric Evan’s ubiquitous language, and Dan North’s given-when-then template. The most visible differences are that the tests here are presented in table format rather than in a more textual format, such as BDD’s Cucumber language, and they concentrate on functionality instead of the user interface. This books’s version of ATDD matches closely that described by
One of the most well-known DDs is
Source : Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration, Ken Pugh
« Origins
• 2003: Kent Beck briefly mentions ATDD in the book “Test Driven Development: By Example” but dismisses it as impractical
• 2003 to 2004: driven by the popularity of Fit/FitNesse ATDD becomes accepted practice in spite of Beck’s objections »
Source : agilealliance.org
« In his recent book “Test-Driven Development”, Kent Beck describes briefly the concept of “ Acceptance-Test Driven Development”, and is broadly sceptical to whether it will work. »
Source : Andersson J., Bache G., Sutton P. (2003) XP with Acceptance-Test Driven Development: A Rewrite Project for a Resource Optimization System. In: Marchesi M., Succi G. (eds) Extreme Programming and Agile Processes in Software Engineering. XP 2003. Lecture Notes in Computer Science, vol 2675. Springer, Berlin, Heidelberg
Bonne journée.
DANS NOS COLLECTIONS :
Ça pourrait vous intéresser :
Commentaires 0
Connectez-vous pour pouvoir commenter.
Se connecter