Acceptance Test Driven Development (ATDD)

If you are working in scrum and you are taking a user story, you want to know that all the requirements are met. Now the team will have to write the test cases to meet all the acceptance criterions.

Whenever the development is going to start, right after then these tests are written and executed instantly, in this way these test cases may face failure. Now the developers have to write the code in order to pass the test cases, and then the tests cases are done again, this time they pass without any hassle.

How does it work

ATDD is known as a practice in which the team that is working together about the test case, collaborates with each other and after distilling it into acceptable test and executes it right before the development. This is said to be the best way as it provides with surety that everybody in the team knows that what are they going to build and from the very start they know that what are they going to get in the end.

Now, it is clear that how much it has importance in agile development process, we can say that it is the core part of the agile development.

When the team members with different views and perspectives get to collaborate with each other on how to implement the functionality then with this practice the desired results can be achieved.

Let us understand it better by knowing the main motive of these discussions, to make it simple they need to discuss these three things about the customers:

  1. What is the main issue we are going to solve?
  2. How are we going to solve this issue?
  3. What about THIS and THAT

They are going to find answers for these questions by keeping the customer’s perspective in mind.

— Slimane Zouggari