BDD in Action: Behavior-Driven Development for the Whole Software Lifecycle

We use BDD at work, and my son recently completed his computer science A-level, with a project that was technically incomplete. I've been trying to persuade him to adopt modern software engineering standards and tools, like using git, and defining unit and system tests in his code, doing test first development. I'm kinda amazed they don't teach this in school & they have kids who think it's a good idea to code by the seat of their pants so to speak. If you use a good code repository, do test first & have your tests describe the behaviour of your code, you eliminate a great deal of project risk. Hopefully this will convince him before his university course starts, to start using sensible tools and techniques.

As a novice to BDD, this was just the book I was looking for. As the book states, it covers the various aspects to BDD throughout the software lifecycle. I would recommend this book to all agile practioners embarking on BDD.

Half way through, and its great.

I not got a clue but she spent all day reading it so assume it's a great book !

Excellent resource for software development professionals. I found it useful in adapting my approach to practicing agile business analysis.

I'm new to BDD and needed a quick start come deeper info. I use TFS, C# and Git, if the book turns out to be a lemon Ill update the review. If you don't hear from me assume its worth buying. First impressions are good, with example of sort of real world projects. I downloaded mine as an ebook direct form Manning. Anyone noticed Amazon book prices going up?

I have to admit I was a little apprehensive about this book before I read it. I've heard so many contradictory ideas about what BDD is... it is the use of real examples, is it simply the use of acceptance criteria with user stories, or simply using a test framework like Cucumber makes you a BDD expert? I'm happy to say this book sets out a very thorough picture of what BDD is, and more importantly why is is useful. The book covers a surprising amount of material, theoretical and practical. From the requirements gathering using Impact Mapping, to how to write and organise Given...When...Then scenarios, through to working with various automation frameworks. It gives a full end-to-end reference guide that would be useful for product managers, developers, and testers alike. And like any good BDD book should be, it's full of realistic examples! For me it's one to keep close at hand for quick reference, I'm finding it useful for brushing up on a bit of theory now and again and helping to remind me of good ways to organise my scenarios. I particularly enjoyed reading about Impact Mapping, Feature Injection, Real Options, and Deliberate Discovery, which were completely new ideas to me. My favourite quote from the book (from Liz Keogh) Uncertainty's the muse of all that's new, And ignorance the space in which she plays;

I love this book. It explains BDD in a very understandable way. I never get tired continue reading it, it was consistenly enjoyable read until the last chapter.

There is always a good book for every well known approach in software engineering. For BDD, this is the one.

Ma société a acquis ce livre pour nous aider à étendre notre connaissance du BDD. Le livre traite de l'"approche BDD" à tous les niveaux, depuis la définition des besoins jusqu'à l'écriture des tests unitaires. L'ouvrage est accessible à tous, extrêmement bien écrit et inclue de nombreux exemples concrets pour mettre les idées en pratique, faisant usage de plusieurs frameworks BDD connus par le milieu. En toute franchise, je recommande chaleureusement l'ouvrage à tous ceux qui veulent fournir des produits applicatifs de qualité, qui répondent vraiment aux besoin des clients. Excellent!

Estou bastante satisfeito com essa aquisição. Este livro realmente servirá como fonte de conhecimento e acrescentará bastante na minha carreira.

I'm a pretty experienced programmer, and lately I've been doing a lot of AngularJS development. Before reading this book, I was a zealous advocate of automated testing with Jasmine and Protractor. After reading this book I've learned that there is another type of automated testing you can throw into the mix- a "high-level test" written in gherkin that is also executed via command line (cucumber.js or yadda for javascript programs). At first I thought, "Jasmine is a "BDD" syntax. Isn't that good enough?", and by the end of this book Smart convinced me that, NO, it's not good enough. Having high-level executable tests 1) makes the tests accessible to all team members (not just the programmers), 2) Can be a single source of truth for code completed and planning, 3) generates "living documentation, and 4) makes your specs more "business value-focused' instead of "checking that my functions work-focused". The awesome thing is that through step functions these high level tests are actually mapped to the good ole' unit tests I've always loved. The one thing I didn't like about this book is that it tries to please everyone. It has the most examples from Java. It also has some from python, ruby, and JavaScript. In some ways I would have rather read a BDD book on only JavaScript, but I still give this book 5 starts because of the new way it has inspired me to approach unit testing and just developing software in general.