'Lean-Agile Acceptance Test-Driven Development' Excerpt
Agile Development is dependent on a testing process that, like requirements themselves, are created and executed in close collaboration with users. This book chapter will walk you through an real-world example of how a ATDD user acceptance test can be planned and executed.
Within the framework of Acceptance Test-Driven-Development (ATDD), customers, developers and testers collaborate to create acceptance tests that thoroughly describe how software should work from the customer's viewpoint. By tightening the links between customers and agile teams, ATDD can significantly improve both software quality and developer productivity.
This is the first start-to-finish, real-world guide to ATDD for every agile project participant. Leading agile consultant Ken Pugh begins with a dialogue among a customer, developer and tester, explaining the "what, why, where, when and how" of ATDD and illuminating the experience of participating in it.
Next, Pugh presents a practical, complete reference to each facet of ATDD, from creating simple tests to evaluating their results. He concludes with five diverse case studies, each identifying a realistic set of problems and challenges with proven solutions.
This excerpt is from Chapter 4, entitled "An Introductory Acceptance Test." It presents an example of an acceptance test and four ways that it can be executed.
This excerpt is reprinted with permission from publisher Addison-Wesley Professional, Copyright 2011, Pearson Education, Inc. It comes from "Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration" by Ken Pugh, ISBN 0321714083, January 2011.
The attached Zip file includes:
- Intro Page.doc
- Cover Sheet and Terms.pdf
- Lean-Agile Acceptance Test-Driven Development Excerpt.pdf