Chapter 10. Acceptance Testing
What’s done, is done.
—Shakespeare, Macbeth, Act 3, scene 2
If it isn’t tested, it doesn’t exist.
—Anonymous agile master
We recently transitioned to agile. But all our testers quit.
—Vignette from Crispin and Gregory 
Why Write About Testing in an Agile Requirements Book?
As a sanity check in preparing for this chapter, I went to my bookshelf and looked at a n...
- Chapter 10. Acceptance Testing
- from Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
- Publisher: Addison-Wesley Professional
- Released: December 2010
In traditional development, requirements are rarely informed by implementation concerns or testing. But in agile development environments, it is important to take a more holistic view. Acceptance testing is a critical component of agile requirements management, and what were once separate activities are now part of a continuous process of refinement. In this lesson, you will familiarize yourself with these principles.
Share this highlighthttp://www.safaribooksonline.com/a/agile-software-requirements/99226/