HomeНаука и техникаRelated VideosMore From: QASymphony

Behavior Driven Development vs. Traditional Development

412 ratings | 47502 views
In this episode of Whiteboard Friday, we address Behavior Driven Development, aka BDD. We'll talk about what BDD is and compare it to a traditional development process. Watch the full Whiteboard Friday series: http://bit.ly/2nxk6kV A traditional development process begins with a stakeholder determining what the business needs are for the product and dictate that to the product owner. The product owner then writes the requirements on his or her own, leaving out the developer and tester. Because they were absent during the requirement writing, the developer and tester must translate the requirement into what actually needs to happen; the developer translates requirements to code, the tester must translate requirements to test cases and technical writer translates into technical documentation. A BDD process begins with the product owner, tester and developer collaborating around the requirements, asking questions and providing examples of the business need. Agreed upon requirements are defined as English-formatted scenarios. In BDD, the developers can then use the scenarios for automated tests and testers also use scenarios as the basis for their tests. The byproduct behavior driven development means moving away from silos to a more collaborative process, resulting in a more complete final product that what a traditional process can deliver. #BDD in a tweet: “Using examples at multiple levels to create a shared understanding and surface uncertainty to deliver software that matters.” -Dan North @tastapod
Html code for embedding videos on your blog
Text Comments (22)
chandu 23rd (6 days ago)
a perfect starter in the foodbox. Thanks much...
Swapnil Gupta (1 month ago)
Something worth to watch, thanks
Susie Q (2 months ago)
This was really good, appreciate it!
freejack1982 (3 months ago)
Perfect, thanks!
Arjuna Nanayakkara (3 months ago)
Thanks for the clip. Nice intro. Are there tools that can plug into JIRA or Confluence that support BDD?
Jugaad Live (5 months ago)
Good one. thanks
Royden Pereira (7 months ago)
good one
Mirza Usman Beg (1 year ago)
Well explained..cleared up confusion in my mind about BDD. Thanks for sharing!!
Abdul (1 year ago)
Really cool video it clearly described BDD ...thanks for making it :) looking forward to watching more videos.
Hunter Harington (1 year ago)
THX WHITEBORADR FRIDEAY. commentaries are essetnail .... inshallah
vroomgc (1 year ago)
Seriously, that is your response...
Chirag Matkar (1 year ago)
great description
Mukta Sharma (1 year ago)
very good...thanks
Katerina Tkachenko (1 year ago)
Looks like you guys have totally forgotten about the existence of Business and System Analysts, who are actually in charge of translating stakeholders' ideas into real technical requirements. Being a developer on a semi-size project you won't be able to have enough input to decide how to correctly implement a feature if it requires integrations with other existing systems (usually not very much documented). Moreover, you will have a lot of communication with non-tech people instead of coding time and this will be most likely a very long-going project with Change Requests. So, I can't understand what problem are people about to solve using BDD? In fact, this is an attempt to distribute a BA role between QA and Dev.
zed (10 months ago)
Not every company has Business Analysts. I don't know about you, but I am a developer, not a coder. My job requires that I spend more time thinking than coding. That means collaborating with QA people and Product Owner to make sure we have as much detailed and complete requirements as possible. The issue we currently have is that the PO writes the requirements in one format. We developers then translate these requirements into code. And QA also translate the requirements into test scenarios. That is a lot of wasted duplicate work and time. If we could have ONE set of requirements definition that are already in a common format for PO, Dev and QA, that would save us a lot of time and fix comprehension issues when it come to requirement written in a non standard format. ...well that is BDD.
vroomgc (1 year ago)
Totally agree Ekaterina, way too many holes in this example. And he doesn't compare it to Agile which is suppose to have more collaborative discussions with the stakeholder and IT team members.
Da Do (1 year ago)
Thats why you have senior and lead developers.
Dreaston Bikrain (1 year ago)
Ekaterina Tkachenko I am currently gathering information about programming and software dev. in general, but videos, articles, etc. like this video - create me a lot of headaches by leaving out important aspects of the process(even though they often contain useful stuff as well or the scenario like in this case is useful for further steps), so thank you for pointing me in the right direction :)
RAHUL KHANNA (2 years ago)
Nice one Ben.. gave me good understanding.
aboumejd younes (2 years ago)
Thanks for sharing BRO !!
Hamsini Sarma (2 years ago)
Short video with full of info. Thanks for sharing.
Rakesh Matha (2 years ago)
worth watch

Would you like to comment?

Join YouTube for a free account, or sign in if you are already a member.