Get Started with Acceptance Test-Driven/Behavior-Driven Development
Defining, understanding, and agreeing on the scope of work to be done are often areas of discomfort for product managers, developers, and quality assurance experts alike. The origin of many items, living in our defect tracking systems, can be traced to our difficulty performing these initial activities. Ken Pugh introduces acceptance test-driven development (ATDD)/behavior driven development (BDD), explains why it works, and outlines the different roles team members play in the process. ATDD/BDD improves communication among customers, developers, and testers. By decreasing re-work, ATDD/BDD has proven to dramatically increase productivity and reduce delays in development. Through interactive exercises, Ken shows how acceptance tests created during requirement analysis decrease ambiguity, increase scenario coverage, help with effort estimation, and act as a measurement of quality. Join Ken to examine issues with automating acceptance tests including how to create test doubles and when to insert them into the process. Explore the quality of tests and how it relates to the underlying code.