ATDD by Example: A Practical Guide to Acceptance Test-Driven Development: A Practical Guide to Acceptance TestDriven Development (AddisonWesley Signature Series

A Kent Beck Signature Book

by Markus Gärtner

With Acceptance Test-Driven Development (ATDD), business customers, testers, and developers can collaborate to produce testable requirements that help them build higher quality software more rapidly. However, ATDD is still widely misunderstood by many practitioners. "ATDD by Example" is the first practical, entry-level, hands-on guide to implementing and successfully applying it. ATDD pioneer Markus Gartner walks readers step by step through deriving the right systems from business users, and then implementing fully automated, functional tests that accurately reflect business requirements, are intelligible to stakeholders, and promote more effective development. Through two end-to-end case studies, Gartner demonstrates how ATDD can be applied using diverse frameworks and languages. Each case study is accompanied by an extensive set of artifacts, including test automation classes, step definitions, and full sample implementations. These realistic examples illuminate ATDD's fundamental principles, show how ATDD fits into the broader development process, highlight tips from Gartner's extensive experience, and identify crucial pitfalls to avoid. Readers will learn to Master the thought processes associated with successful ATDD implementationUse ATDD with Cucumber to describe software in ways businesspeople can understand Test web pages using ATDD toolsBring ATDD to Java with the FitNesse wiki-based acceptance test framework Use examples more effectively in Behavior-Driven Development (BDD)Specify software collaboratively through innovative workshopsImplement more user-friendly and collaborative test automationTest more cleanly, listen to test results, and refactor tests for greater value If you're a tester, analyst, developer, or project manager, this book offers a concrete foundation for achieving real benefits with ATDD now-and it will help you reap even more value as you gain experience.

Genres: Software, Technology, Programming, Computer Science, Technical, Reference

236 pages, Paperback

First published July 12, 2012

About the author

Markus Gärtner works as an Agile tester, trainer, coach and consultant with it-agile GmbH, Hamburg, Germany. Markus founded the German Agile Testing and Exploratory workshop in 2011, is one of the founders of the European chapter in Weekend Testing, a black-belt instructor in the Miagi-Do school of Software Testing, contributes to the Agile Alliance FTT-Patterns writing community as well as the Software Craftsmanship movement. Markus regularly presents at Agile and testing conferences all over the globe, as well as dedicating himself to writing about testing, foremost in an Agile context.

Reviews

[Torben Rasmussen · Rating 4 out of 5]

ATDD by Example is an excellent primer on Acceptance Test Driven Development. The author switches fluently between detailed technical considerations on how to automated functional tests and the higher level abstractions and testing techniques that underlies it.
Exactly this seems to become the books weak side. It requires a solid understanding of both programming and testing to be really valuable, a combination of skills that is still all too rare.
This may confuse some readers that would either need to have a stronger focus on the underlying testing techniques and an introduction to ATDD or more focus on the actual test implementation in code. For the former I strong recommend Specification by Example by Gojko Adzik. For the the latter this seems to be a good starting point and a number of online resources can be used to further explore this subject.
Markus Gärtner have written a good book on this subject that nicely complements the body of litterature on this subject. It is recommmended reading for anyone who are concerned with automated testing. I give it 4/5.

[Christophe Addinquy · Rating 1 out of 5]

This book is a clear disappointment. It's about looking at ATDD from a developper perspective alone. Because you know, we're developers and we're the smartest guys in the room. And everybody else sucks. ATDD is a specification activity, a way to create shared understanding among the project actors. Instead the book focus heavily on code (not very well also), using Fitness and Selenium. I don't care about it or I would purchase a Selenium book.
The parts of the book dedicated to the real Specification by example activity are poorly borrowed from Gojko Adzic. So read Gojko's book instead.
ma note de lecture en français ici

[Alf Kåre Lefdal · Rating 3 out of 5]

The book is OK. I enjoyed the first part, which is similar to the first part of Kent Beck's TDD book. The rest of the book did not add much more value than Gojko Adzic's SBE book.

[Kim · Rating 4 out of 5]

Very clear and practical book that got me started right away.

[Elias Nogueira · Rating 4 out of 5]

Great book showing what is ATDD in the fists chapters in a light way.

[Christoph Kappel · Rating 4 out of 5]

I usually don't read translated books, when I am able to understand the native language, but too bad I noticed this too late.

That said, this book was interesting. It started with a comparison of Cucumber and FitNesse in two dummy projects, although the first one was pretty short and I don't fully agree with the handling of the traffic lights.

The later chapter gave more theory about the whole process and the way of thinking.

Overall pretty recommended, if you want to have a brief introduction into the whole "Specification by Example" idea and the book contains lots of ideas for further reads.

[gargamelscat · Rating 2 out of 5]

Maybe it was a game-changer when it came out and the first 1/3 is engaging enough and a quick read.

But the central part with the worked example of test driving development of a traffic light management problem was not well described making relating the justification to the code changes hard to understand. (by contrast for an outstanding book on this kind of thing James Grenning's book on testing embedded systems is excellent).

The final 1/3 seemed like a bunch of common-sense platitudes that were not particularly actionable.

[Nathaniel Inman · Rating 2 out of 5]

"A tool is not a strategy." The best line from the book is actually a quote from a separate book: Lessons Learned in Software Testing. If you were unfortunate enough to pick up this book and decide to read it, I'd advise skipping to section 3 where all of the "meat" is. As it stands this would have been better served as a blog post. The organization is lacking, the examples aren't great, the conversations to purvey pair programming or teamwork are contrived and it's chock-full of filler text.

[Johnny · Rating 3 out of 5]

A well written starting guide on the topic of acceptance test-driven development. The book shows the basic topics and helps you to make your first steps with ATTD. The examples are realistic and help you to understand how this style of testing is different from other approaches. However, by aiming at beginners it will not cover intermediate topics.

[Olha]

https://drive.google.com/open?id=1nHp...

[Shenyu · Rating 3 out of 5]

A book introduces some basic knowledge of ATDD and usage of cucumber as well as FitNesse. This book is generally okay, but some parts appear to be outdated or difficult to understand.

[Chris Jansson · Rating 2 out of 5]

Read goos instead

[Pavel Skorodzievskiy · Rating 3 out of 5]

Can be useful mainly for beginners. If you had experience on few projects with automation testing/tdd before, this book has little to offer you.

[Vladislav · Rating 4 out of 5]

A good ATDD primer for beginners. Those who have already experienced ATDD or have read "Specification by Example", "The RSpec Book" and "The Cucumber Book" would uncover few secrets. Although I have to admit that Part 3 about principles and values is a good summary to refer to if you need to quickly refresh your memory or teach someone else the ATDD discipline.

[Matteo Tomasulo · Rating 2 out of 5]

On piratical side, just ok to see a little bit how to combine ATDD and TDD and have a introduction on different tools (Part I and Part II).
On the conceptual/principle side I did not find nothing very interesting or useful.

[Marek · Rating 3 out of 5]

very nice primer, just sometimes violating the DRY principle.

[Nick Zdunic · Rating 4 out of 5]

Fairly good in that in provide technical examples whilst others haven't.