Acceptance Test Driven Development as a methodology for writing down software requirments as a test.
ATDDis not only a development method but also a good layer of communication between the developers of those who gather the requirements, those who develop and test the software

- What is ATDD
- The difference between Acceptance Test Driven Development and Behavior Driven Development
- The difference beteween ATDDand usual Test Driven Development
- Basics of the Gherkin Given When Then Language
- Writing down requirements in the Gherkin Language

We're gonna play a bowling game, and by that we learn how to use the ATDD approach to write a software to calculate the results. ATDD is an approach within the BDD methodology. After this tutorial attendees will describe features using the gherkin language and implement them a test cases using Behat. ATDDis the Business version of Test Driven Development


- Acceptance TestDriven Development vs Behavior Driven Development
- Test Driven Development and Acceptance TestDriven Development where is the difference

This course has been tested at PHP Conference London 2019 in a workshop format.

Code of the course is downloadable and available on GitLab,
if you did the exercise and would like an eye on your code feel free to contact me always hapy about feedback.