Posted by johnsmart
on October 21, 2012 at 3:45 AM PDT
Acceptance Test Driven Development (ATDD) is a method wherein business stakeholders, analysts, testers and developers collectively specify and agree on what needs to be completed in the project.
Acceptance Test Driven Development (ATDD) is a method wherein business stakeholders, analysts, testers and developers collectively specify and agree on what needs to be completed in the project. Requirement specifications are set and verified even before actual development starts. This ensures that only those value-adding features are delivered to the business.
Instead of validating after the feature has been developed, tests in ATDD are embedded throughout the development process. This gives immediate feedback should there be any discrepancies between documentation and actual implementation. With this in practice, the product is better tested having team effort and time put into their best use.
In the upcoming Devoxx conference, I will share how tools such as JBehave and Thucydides can help you form well-written acceptance tests. You will also get to know the benefits of having well-written tests to your documentation and reports.
What is important to highlight in ATDD is that collaboration is key to successful development. As I would put it, ATDD is a simple process change that can have far-reaching implications for your development projects.