1. Find answer...
   1. Will the stakeholder agree to this format?
   2. Who will write the scripts
      1. Training?
         1. Start with "BDD in Action"
   3. What tools will be used
      1. How will the scripts be stored
   4. How to build the whole process
   5. Will the scripts be a part of CI / CD?
2. ideal
   1. For discovering, illustrating, and verifying business requirements
      1. Team and Stakeholders understand a scenario
      2. We receive a clear and objective goal for each US
      3. Helps Team, Stakeholder, Customers to know what will be built
   2. For further automation
3. WHY
   1. There is FOCUCED and LIVING documentation
   2. Team and Stakeholder FOCUS on the Features, that deliver business value to customer
      1. We will think how users interact with our system and what the outcomes should be
   3. Most BDD tools are FREE!
      1. You can choose appropriate tool for your context
4. Benefits of BDD
   1. Reduced wastes and costs
   2. Easier and safer changes
   3. More flexible development and testing
   4. Faster releases
   5. BDD works in Agile
   6. More communications
      1. WORK TOGETHER TO SPECIFY FEATURES
   7. Better understanding of the high-level goals of your application
   8. One of the steps to the Continuous Improvement
5. Disadvantages and potential challenges of BDD
   1. BDD requires high business engagement and collaboration
   2. BDD requires time for development and maintaining
   3. BDD requires a high Team level of interaction
   4. The stakeholder should be able to formally describe the scenarios
   5. Problems in describing of complex scenarios
6. Pattern
   1. Given
      1. All the preconditions/steps that must have occurred
   2. When
      1. Execution of the even/action, which we are testing
   3. Then
      1. We describe what outcome we expect
7. Some Tips
   1. Remember
      1. The Cardinal Rule of BDD
         1. One Scenario, One Behavior!
      2. The Golden Gherkin Rule
         1. To treat other readers as you would want to be treated
         2. Write Gherkin so that people who don’t know the feature will understand it
   2. Avoid dependencies between scenarios
   3. Use data tables and table-driven approach
      1. Use Test Design techniques to obtain data
   4. Scenarios can be completed with background data
   5. The BDD scenario should be
      1. Focused
      2. Concrete
      3. Important
      4. Clear
      5. No
         1. emotions
         2. assumptions
         3. guesses