Test driven development (TDD) is an evolutionary approach to development that relies on the repetition of short development cycle. Behavior driven development (BDD) is an amalgamation of practices stemming from test driven development.

1. Test driven development
vs
Behavior driven development
Software Testing Insights

2. Test driven development vs Behavior driven development
Trying to take a decision on which method to use for your application development? Then Read on.

3. Test driven development vs Behavior driven development
• Test driven development, as the name implies, is driven by a number of
tests.
• After a unit test is written, it is then run against a code that is as yet
unwritten.
• The problem here is that the code itself is bound to be full of bugs
• No organization wants to waste resources, which is why it’s doubly
important to assess when and for what purposes one should employ unit
tests.
This is where the Behavior driven development comes in…

4. Test driven development vs Behavior driven development
• Behavior driven development is a process refinement over the Test Driven
Development (TDD) and Acceptance Test Driven Development (ATDD)
• BDD makes it easier to develop a consistent vocabulary for analysts,
testers, and developers, and eases business processes.
• BDD primarily focuses on reaching out a clear understanding of the desired
software behavior through consolidated discussions with the stakeholders.

5. You can Read More at: http://bit.ly/1Ne9y41
Choosing between TDD and BDD boils down to the nature of your framework and your target
language. So choose wisely when it comes to TDD or BDD.
Test driven development vs Behavior driven development