- Taschenbuch: 353 Seiten
- Verlag: Manning; Auflage: Pap/Psc (9. Oktober 2014)
- Sprache: Englisch
- ISBN-10: 161729165X
- ISBN-13: 978-1617291654
- Größe und/oder Gewicht: 23,4 x 18,8 x 1,8 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 74.166 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
BDD in Action (Englisch) Taschenbuch – 9. Oktober 2014
Wird oft zusammen gekauft
Kunden, die diesen Artikel gekauft haben, kauften auch
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Über den Autor und weitere Mitwirkende
AUTHOR BIO John Ferguson Smart is a specialist in BDD, automated testing, and software life cycle development optimization. A well-known speaker and writer, John is the author of Java Power Tools and Jenkins: The Definitive Guide.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
* Where to start in the process
* What to test and what not to test
* How much to test in one go
* What to call the tests
* How to understand why a test fails
The traditional development process provides many opportunities for misunderstandings and miscommunication. BDD in action presents the process how software development should be managed by both business interests and technical insight. Behavior-Driven Development (BDD) encourages teams to use conversation and concrete examples to build up a shared understanding of how an application should work and which features really matter. BDD in Action is a great introduction to Behavior Driven Development.
This is what I liked about the book:
* Presentation of Behavior Driven Development theory with real world practical approach to make readers comfortable and have a quick grasp on the subject
* Book does a good job defining the BDD principles and practices. The books shows you how to integrate them into your existing development process
* How to use BDD for acceptance, integration, and unit testing
* The book goes beyond introduction with inclusion of advance topics such as living documentation, running parallel acceptance tests, and continuous integration
None, that I am aware of
Wish list for next edition:
Inclusion of some guidance to the user for choosing a BDD tool.
Disclaimer: As a volunteer reviewer, I received a complimentary copy of the eBook from Manning.
BDD techniques can be brought into virtually any software development method and help you build and deliver better software. "The traditional software development process offers many opportunities for misunderstandings and miscommunication," Smart writes.
One of the key approaches in BDD, therefore, is to get a project's major stakeholders to talk to each other AND work together to develop concrete examples of what each feature should do and how the desired software should behave.
You want software "that works well and is easy to change and maintain...." But you also don't want to waste thousands or millions of dollars on creating software that does not provide "real value to its users."
BDD, the author points out, "is a set of software engineering practices designed to help teams build and deliver more valuable, higher quality software faster. It draws on Agile and lean practices including, in particular, Test-Driven Development (TDD) and Domain-Driven Design (DDD. But most importantly, BDD provides a common language based on simple, structured sentences expressed in English (or in the native language of the stakeholders) that facilitates communications between project team members and business stakeholders."
The author describes and shows how to put BDD into action in real-world settings. If you work in software development or are hoping to land a job there, you likely need to read this book and keep it handy.
I thought I might as well start the review by including this quote from the Foreword to BDD in Action, by Dan North (the original creator of Behaviour-Driven Development), because it sums up exactly what I agree John Smart has succeeded in doing. In an environment where there are still lots of new ideas being thrown around, often just in blogs or conference talks and the like, Smart has managed to consolidate the heart of BDD into one comprehensive book. In particular, whereas many books on BDD focus on one tool with with a bit of theory, Smart manages to provide more than sufficient instruction in a range of tools (including JBehave, Cucumber-JVM, SpecFlow, Cucumber-JS, Spock, Thucydides), and yet still undergird that with a “solid theoretical foundation”.
BDD is a very hot topic in software development today. It is an approach based on the seemingly simple premise of focusing on developing software that directly meets business goals. The increasing widespread adoption of agile methodologies has provided a stage for the necessary collaboration and fast feedback loops that make BDD viable and many organisations are seeing the benefits of adopting some, if not all, of the practices associated with BDD (whether they call it BDD or Acceptance Test-Driven Development or Specification by example or call it no special name at all). BDD in Action addresses all of the principle BDD activities, i.e. deriving features from business goals, illustrating features with examples, creating executable specifications to guide development, automating specifications and producing living documentation. In the process, other key contributions to BDD techniques (by the likes of Gojko Adzic, Chris Matts, et al.) are explained in just enough detail to enable the beginner to get started, while providing a handy reference for the BDD practitioner with some experience.
Working systematically through the BDD activities, Smart provides excellent signposting, examples and illustrations to keep the reader on track. In particular, A BDD approach is traced, from business goals to living documentation, on the fictitious ‘Flying High Airlines’ business, which is a tremendous help in providing concrete examples of how the theory works out.The repeated use of a diagram describing the principles activities, as they evolve through each chapter, is also very instructive.
The decision to deal with a variety of tools, rather than focus on just one or two, really increases the value of the book. Often the same exercise is demonstrated in different tools and for those who haven’t already committed to tools, it is a concise comparative guide to the features of different tools. For those who have already got a preference on tools, it will be a great benefit that the book cover’s the main tools more than adequately (avoiding having to try to translate Smart’s excellently structured content to another tool themselves).
BDD in Action is a very practical, hands-on manual for BDD practitioners. I see it as a great introduction for those embarking on this path and the kind of handbook that will be left out by development teams to refer to regularly. It doesn’t try to sell BDD, so other literature on case studies et al. may be better for that, but it is no doubt destined to become the definitive BDD manual for the foreseeable future.
The book I would recommend to everyone: business analysts, program managers, software developers and testers.
Virtually to everyone. Why? Because BDD method introduce some order, makes easy communication between different specializations and even non technical business people. It makes whole development process clear, coherent and up-to-date.
I would strongly recommend a method and the book of course to agile practitioners. The book apart from technical details which maybe no so interesting to non-technical people. Shows how to properly construct projects how to define, features, stories, examples. It contains tips and guidelines how to make common interface between different walk of life people. How it should differ from "classical" approach when customer originally wanted something, business analyst understand it differently then he tried to explain story to technical stuff, but not having all knowledge including technical. And then developers misunderstood BA and development prepared in turn suboptimal solution. At last customer got something different that he expected. Time, money, effort are frequently wasted. But this could be avoided provided that every link of process would be aware what should be prepared.
BDD unites somehow Design driven development and test driven development, gives living documentation in English which in turn can be easily transformed to examples and then to features and user stories. Everything is going to be transparent. And misunderstanding and domain knowledge and what user really needs can be controlled and corrected at every development stage.
This is great approach and very promising I would like that many people would read that book and improve their process. I now tat sounds maybe overly optimistic but I think knowledge inside BDD in Action is quite powerful.
It starts with a very general description of BDD, the problems that it addresses, the general principles and the origins of it, as well as the pros and cons in different organisations and team scenarios. Throughout this general description there are plenty of references and links for anyone wishing to have more details.
This is followed by a real life project, that goes through the phases of requirement analysis, creation of the features, stories and examples and the distinction and differences between each of them. There are various techniques described, including Feature Injection for identifying business goals and supporting features, Impact Mapping for high-level requirement visualisation, Purpose-Based Alignment Model for judging how much effort you should put into different features, and the identification of stakeholders and their roles. There is also a description about Real Options and Deliberate Discovery principles.
Last but not least, there is a chapter dedicated to explaining the relationship between BDD, TDD and Unit Testing, another one describing the idea of living documentation, as well as reporting and project management, and finally the role of BDD in continuous integration (CI) and continuous delivery.
Throughout the text there are a lot of diagrams to help explain the ideas better, as well as a lot of references for more detail. Even though most of the examples are based in Java, the principles, ideas and techniques are easily applied to other languages and tools.
So, in summary this is a very useful book for anyone wanting to learn how Behaviour Driven Development can be used in practise. There are different sections that are targeted to different roles from business stakeholders, to testers and to developers. Hopefully when your whole team reads this book, the whole idea of BDD can be understood better, and <strong>used to build the software right as well as build the right software.</strong>
Disclaimer: This book was reviewd under the Manning reviewers program.
Ähnliche Artikel finden
- Fremdsprachige Bücher > Computer & Internet > Informatik > Systemanalyse & Design
- Fremdsprachige Bücher > Computer & Internet > Programmieren > Java
- Fremdsprachige Bücher > Computer & Internet > Programmieren > Software-Design & Entwicklung > Softwareentwicklung
- Fremdsprachige Bücher > Computer & Internet > Programmieren > Sprachen & Tools
- Fremdsprachige Bücher > Computer & Internet > Projektmanagement