[1/2] ATDD by Example: A Practical Guide to Acceptance Test-Driven Development (ATDD. Software development through acceptance tests) (Category Engineering)

I re-read this book by Marcus Gärtner a decade ago about approaches to development through acceptance tests. At that time, I had just met BDD. (behavioral driven development). More specifically with Cucumber, and then read about ATDD. Now the book is still relevant at the conceptual level, but the manual work of compiling acceptance tests threatens to take over LLM models, see for example whitepaper.Acceptance Test Generation with Large Language Models: An Industrial Case Studyfrom April 2025 A year in which a two-step approach is proposed

(i) generating acceptance test scenarios in natural language (in Gherkin) from user stories, and (ii) converting these scenarios into executable test scripts (in Cypress), knowing the HTML code of the pages under test

If we talk about the book itself, then this is an entry-level practical guide to the implementation and successful application of the ATDD technique. The main goal of the work is to show how customers, developers and qa engineers can jointly create testable requirements, which allows you to create high-quality software in a short time. The author demonstrates the fundamental principles of ATDD through two end-to-end cases: a system for paying for parking, and a system for controlling traffic lights. He then describes the basic principles of ATDD and how to implement it in organizations. In the first case, Ruby, Cucumber and Selenium are used for automation, in the second part, examples are implemented in Java using FitNesse. Each case is accompanied by an extensive set of artifacts, including test automation classes, step definitions, and full implementations.

More about the content of the book in next post.

#QA #DevOps #Process #Software #Engineering #AI