Converting a requirement into executable tests – BDT

This session will brief about the gaps that generally exist between managment and technical team memebrs. Here we will focus on how we can use Behavior driven development to fill this gap and can involve non-technical persons also in the development phase.

This will brief about how all the stakeholders in the development process (whether technical or non-technical) can be brought on the same page by using Behavior Driven Development.

2 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

  • Why Behaviors ?
  • What is BDD/BDT?
  • Who all are involved in BDD process?
  • Involving management in Development/Testing.
  • How does BDT help ?
  • BDD/BDT Tools and Techniques.
  • Requirement and Test mapping in BDT.
  • Demo of BDT using JBehave.

Learning Outcome

How to involve both technical and non-techincal in the development/testing phases.

Practical Knowledge about behavior driven development and testing.

Target Audience

Developers and Test Engineers

schedule Submitted 4 years ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Naresh Jain
    By Naresh Jain  ~  4 years ago
    reply Reply

    Ravinder, thanks for the proposal. If I'm not wrong, you seem to be using BDD and BDT interchangeably. Is that correct? 

    Your slides are not accessible. Can you please check?

    Also would it be possible to provide links to some BDD spec examples that you've written on a real world project?

    • Liked Anirudh Bhatnagar

      Anirudh Bhatnagar - Continuous delivery in enterprise - devOps and other challenges

      20 Mins
      Experience Report

      Enterprise customers are very different than the cool startups and small companies.

      Sometimes the whole problem statement which build the basis of implementation in one organisation is discarded completely in the other company.

      So in this talk we will take up top 5 challenges which we faced in our projects while implementing continuos delivery.

      1. We wil talk about devOps landscape.

      2. Open Source tools vs Propertery ones.

      3. The trust in automation - how did we manage to gain trust of traditional management in automated delivery.

      4. The tale of Product Owners - how did we manage to assign the role of product owner in a traditional project management company.

      5. And of course, the mindset

      All these real project scnerios and how did we solved them will be addressed in this experience report.