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 [2009]

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 number of texts on software requirements management, including my own [Leffingwell and Widrig 2003], for guidance on testing whether an application meets its requirements. Of course, I knew I wouldn’t find much on testing there, if for no other reason than I knew I hadn’t written much. I wasn’t surprised that other requirements authors haven’t ...

Get Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.