There is an approach to software development where people with different perspectives collaborate to write acceptance tests before implementing a particular feature, with emphasis on the perspective of an customer or end user. In Acceptance Test Driven Development (ATDD), a common method is have people with different backgrounds and expertise involved with writing tests. For example, tests can be written with the following three points of view in mind: 1. customer – what problem are we trying to solve/what user need are we trying to address?; 2. development – what approach might we take to solving this problem?; and 3. testing – how will we know that we’ve solved the problem? The acceptance tests ultimately must represent the user’s point of view and act as a way to describe how the system will function. The tests also serve as a means of verifying that the system functions as intended.
Acceptance Test Driven Development Video
Acceptance Test Driven Development Podcasts
Acceptance Test Driven Development Example
Authored by Philip Rogers
Agile World Resources are provided as free resources to anyone seeking to learn more and are shared under a creative commons attribution license. This means if you use a resource elsewhere you must name Agile World Resources as the source, who the author is, and the photo creator (if used).