From the wikipedia article on BDD:
BDD is a second-generation, outside-in, pull-based, multiple-stakeholder, multiple-scale, high-automation, agile methodology. It describes a cycle of interactions with well-defined outputs, resulting in the delivery of working, tested software that matters.
I am not able to make sense of the adjectives used such as "outside-in", "pull-based" and "multiple-scale" even after going through the referred presentation. Please help explain.
I wrote a blog post on where I learned about BDD as couple of weeks ago. It focus on the .NET platform toolwise and is a bit Cucumber heavy since I like it, but you can pick out some BDD/ATDD stuff from there as well.
When it comes to articles and books I second the suggestions above - it's starts there!
But you should also checkout:
- Introducing BDD
- What's in a story
- The RSpec book
- The GOOS Book
- The Cucumber site with CukeTV that I have found a great resource
Well - there you have it. My short list for things to read.
In addition to the other answers, I have found the following links useful:
outside-in: http://www.courageousmarketing.com/pdf/outsidein.pdf
pull-based: http://www.johnhagel.com/paper_pushpull.pdf
The original article by Dan North about BDD may help: http://dannorth.net/introducing-bdd/
EDIT: Here's an article which breaks down each term:
Behavior driven development is similar to TDD software process but the advantage of BDD is that the tests/features are written in simple English language thus it give a chance to QA and stakeholder to participate in the process of development. It is focused on the behavior of the software thus test are run in browsers.
Here is the guide that explain BDD and its implementation very well. BDD Introduction and Implementation
You can use behat, browserstack to implement BDD in your development process.
来源：https://stackoverflow.com/questions/7399485/understanding-behavior-driven-development-bdd