Ken Pugh, Net Objectives,
Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, developers and quality assurance experts alike. The origin of many items living in our defect tracking systems can be tracked to the difficulty of performing these initial activities. Acceptance Testing roots out these defects by reexamining the process we use to define the work to be done and how it is tested.
This session introduces acceptance testing; explain why it works; and outline the different roles the team members play in the process. We will contrast acceptance testing with unit testing and show examples of how the process clarifies the work to be done.
Target audience: Beginning