Behavior driven development_tutorial
- 2. Behavior Driven Development i AbouttheTutorial Behavior Driven Development (BDD) is a software development process that originally emerged from Test Driven Development (TDD). BDD uses examples to illustrate the behavior of the system that are written in a readable and understandable language for everyone involved in the development. Audience BDD focuses on providing a shared process and shared tools promoting communication among software developers and business analysts to collaborate on software development, with the aim of delivering products with business value. Hence, this tutorial is going to be useful for software developers as well as business analysts at every level. Prerequisites Before you start proceeding with this tutorial, we are assuming that you are already aware of the basics of testing and have some hands-on experience of some testing tools. If you are not well aware of these concepts, then we will suggest you to go through our short tutorial Software Testing. Copyright&Disclaimer Copyright 2016 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected]
- 3. Behavior Driven Development ii TableofContents About the Tutorial ............................................................................................................................................i Audience...........................................................................................................................................................i Prerequisites.....................................................................................................................................................i Copyright & Disclaimer.....................................................................................................................................i Table of Contents ............................................................................................................................................ ii 1. BDD – Introduction ...................................................................................................................................1 BDD – Key features..........................................................................................................................................1 Origin of BDD...................................................................................................................................................1 BDD Practices ..................................................................................................................................................2 Agile BDD.........................................................................................................................................................2 Agile Manifesto and BDD.................................................................................................................................3 2. BDD – Test Driven Development...............................................................................................................4 Why Testing?...................................................................................................................................................4 Challenges with Test-Last Approach................................................................................................................5 Test-First Approach .........................................................................................................................................5 Red-Green-Refactor Cycle ...............................................................................................................................6 TDD Process Steps ...........................................................................................................................................7 Advantages of TDD ..........................................................................................................................................7 Disadvantages of TDD......................................................................................................................................8 Misconceptions about TDD .............................................................................................................................8 Acceptance TDD ..............................................................................................................................................9 TDD Vs BDD ...................................................................................................................................................10 3. BDD – TDD in a BDD Way........................................................................................................................11 Story and Scenarios .......................................................................................................................................12 Development Cycle........................................................................................................................................12 4. BDD – Specifications by Example ............................................................................................................14 Specification by Example – Overview............................................................................................................14 Use of SbE......................................................................................................................................................14 Advantages of SbE .........................................................................................................................................15 Applications of SbE........................................................................................................................................15 SbE and Acceptance Testing..........................................................................................................................15 SbE – A Set of Process Patterns.....................................................................................................................16 Collaborative Specification............................................................................................................................17 Illustrating Specification using Examples.......................................................................................................17 Refining the Specification..............................................................................................................................18 Automating Examples....................................................................................................................................18 Validating Frequently ....................................................................................................................................18 Living Documentation....................................................................................................................................19 Anti-patterns .................................................................................................................................................19 Solution to the Problems - Quality ................................................................................................................20 Tools ..............................................................................................................................................................21 5. BDD – Tools.............................................................................................................................................22 Cucumber ......................................................................................................................................................22 SpecFlow........................................................................................................................................................23
- 4. Behavior Driven Development iii Behave...........................................................................................................................................................23 Lettuce...........................................................................................................................................................23 Concordion ....................................................................................................................................................24 6. BDD – BDD and Cucumber ......................................................................................................................25 Typical Cucumber Acceptance Test...............................................................................................................26 Working of Cucumber ...................................................................................................................................26 Mapping Steps and Step Definitions .............................................................................................................27 7. BDD – Gherkin ........................................................................................................................................30 Gherkin Format and Syntax...........................................................................................................................30 8. BDD – BDD and SpecFlow........................................................................................................................34 Feature Elements and SpecFlow ...................................................................................................................34 Multiple Scenario Steps.................................................................................................................................34 Tags................................................................................................................................................................35 Scenario Outlines...........................................................................................................................................35
- 5. Behavior Driven Development 4 Behavior Driven Development (BDD) is a software development process that originally emerged from Test Driven Development (TDD). According to Dan North, who is responsible for the evolution of BDD, “BDD is using examples at multiple levels to create a shared understanding and surface uncertainty to deliver software that matter.” BDD uses examples to illustrate the behavior of the system that are written in a readable and understandable language for everyone involved in the development. These examples include – Converted into executable specifications. Used as the acceptance tests. BDD–Keyfeatures Behavior Driven Development focuses on – Providing a shared process and shared tools promoting communication to the software developers, business analysts and stakeholders to collaborate on software development, with the aim of delivering product with business value. What a system should do and not on how it should be implemented. Providing better readability and visibility. Verifying not only the working of the software but also that it meets the customer’s expectations. OriginofBDD The cost to fix a defect increases multifold if the defect is not detected at the right time and fixed as and when it is detected. Consider the following example. BDD – Introduction
- 6. Behavior Driven Development 5 This shows that unless requirements are obtained correctly, it would be expensive to fix the defects resulting from misunderstanding the requirements at a later stage. Further, the end product may not meet the customer’s expectations. The need of the hour is a development approach that – Is based on the requirements. Focuses on requirements throughout the development. Ensures that the requirements are met. A development approach that can take care of the above-mentioned requirements is BDD. Thus, Behavior Driven Development – Derives examples of different expected behaviors of the system. Enables writing the examples in a language using the business domain terms to ensure easy understanding by everyone involved in the development including the customers. Gets the examples ratified with customer from time to time by means of conversations. Focuses on the customer requirements (examples) throughout the development. Uses examples as acceptance tests. BDDPractices The two main practices of BDD are – Specification by Example (SbE) Test Driven Development (TDD) Specification by Example Specification by Example (SbE) uses examples in conversations to illustrate the business rules and the behavior of the software to be built. Specification by Example enables the product owners, business analysts, testers and the developers to eliminate common misunderstandings about the business requirements. Test Driven Development Test Driven Development, in the context of BDD, turns examples into human readable, executable specifications. The developers use these specifications as a guide to implement increments of new functionality. This, results in a lean codebase and a suite of automated regression tests that keep the maintenance costs low throughout the lifetime of the software.
- 7. Behavior Driven Development 6 AgileBDD In Agile software development, BDD method is used to come to a common understanding on the pending specifications. The following steps are executed in Agile BDD – The developers and the product owner collaboratively write pending specifications in a plain text editor. The product owner specifies the behaviors they expect from the system. The developers – o Fill the specifications with these behavior details. o Ask questions based on their understanding of the system. The current system behaviors are considered to see if the new feature will break any of the existing features. AgileManifestoandBDD The Agile Manifesto states the following – We are uncovering better ways of developing software by doing it and helping others do it. Through this work, we have come to value – Individuals and interactions over Processes and tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan That is, while there is value in the items on the right, we value the items on the left more. BDD aligns itself to the Agile manifesto as follows – Agile Manifesto BDD Alignment Individuals and interactions over processes and tools. BDD is about having conversations. Working software over comprehensive documentation. BDD focuses on making it easy to create software that is of business value. Customer collaboration over contract negotiation. BDD focuses on scenarios based on ideas with continuous communication with the customer as the development progresses. It is not based on any promises.
- 8. Behavior Driven Development 7 Agile Manifesto BDD Alignment Responding to change over following a plan. BDD focuses on continuous communication and collaboration that facilitates absorption of changes.
- 9. Behavior Driven Development 8 When you look at any reference on Behavior Driven Development, you will find the usage of phrases such as “BDD is derived from TDD”, “BDD and TDD”. To know how BDD came into existence, why it is said to be derived from TDD and what is BDD and TDD, you have to have an understanding of TDD. WhyTesting? To start, let us get into the fundamentals of testing. The purpose of testing is to ensure that the system that is built is working as expected. Consider the following example. Hence, by experience we have learnt that uncovering a defect as and when it is introduced and fixing it immediately would be cost effective. Therefore, there is a necessity of writing test cases at every stage of development and testing. This is what our traditional testing practices have taught us, which is often termed as Test-early. BDD – Test Driven Development
- 10. Behavior Driven Development 9 This testing approach is termed as the Test-Last approach as testing is done after the completion of a stage.
- 11. Behavior Driven Development 10 End of ebook preview If you liked what you saw… Buy it from our store @ https://store.tutorialspoint.com