2011
Pearson Education, Inc.
Ken Pugh
ISBN: 978-0-321-71408-4, 0-321-71408-3
368 pages
PDF
English
Developing software with testable requirements is the theme of this book. A testable requirement is one with an acceptance test. Acceptance tests drive the development of the software. As many development groups have experienced, creating acceptance tests prior to implementing requirements decreases defects and improves productivity. (See the Epilogue for examples.) A triad—the customer/business analyst, developer, and tester—collaborates on producing these tests to clarify what is to be done. In creating a high-quality product, ATDD is as much about this clarification as it is about the actual testing.
As an example, do you have criteria in mind as to whether this book will meet your needs? If you finish this book, how will you know whether it has met those criteria? This book represents an implementation of something that should meet your needs. Because you are reading this book after its completion, you don’t have an opportunity to influence the acceptance criteria. But let me list the criteria here and see if this is what you are after.
In English classes, the teacher emphasized that a story should contain a who, what, when, where, why, and how. So I’ve made that the goal of this book. It explains
- Who creates acceptance tests
- What acceptance tests are
- When the acceptance tests should be created
- Where the acceptance tests are used
- Why acceptance test-driven development is beneficial
- How the acceptance tests are created
By the end of this book, the expectation is that you should understand how testable requirements can make the software development process more enjoyable (or at least less painful) and help in producing higher-quality products., Let’s begin with a brief discussion on the why, what, where, and who issues.

Download File Size:2.78 MB

---