Comments on: TDD vs BDD

By: Evolution of test automation frameworks - from spaghetti to cucumber | Cognifide Blog

Tue, 25 Jun 2013 21:58:39 +0000

[…] http://blog.mattwynne.net/2012/11/20/tdd-vs-bdd/ […]

By: Clifton Ramos

Clifton Ramos — Tue, 14 May 2013 19:50:18 +0000

This definition is rather non-specific in that it allows tests in terms of high-level software requirements, low-level technical details or anything in between. The original developer of BDD (Dan North) came up with the notion of BDD because he was dissatisfied with the lack of any specification within TDD of what should be tested and how.

By: Rounded Corners 380 â€” Heisenberg Uncertainty Principle | Labnotes

Rounded Corners 380 â€” Heisenberg Uncertainty Principle | Labnotes — Wed, 12 Dec 2012 15:45:58 +0000

[...] Â§Â TDD vs BDD. My one key take away: This misses out of the major benefit of working outside-in, which is having the requirement challenged: if you need to explain to a computer how to check the requirement, youâ€ll need to be damn sure understand it yourself. If you donâ€t (and you often donâ€t) itâ€s much cheaper to find that out before you write the code. [...]

By: Manuel Pais

Manuel Pais — Wed, 21 Nov 2012 14:15:21 +0000

There were also some interesting points in another InfoQ virtual panel on TDD/BDD:
http://www.infoq.com/articles/virtual-panel-tdd-bdd

By: Five Blogs â€“ 21 November 2012 « 5blogs

Five Blogs â€“ 21 November 2012 « 5blogs — Wed, 21 Nov 2012 05:43:38 +0000

[...] TDD vs BDD Written by: Matt Wynne [...]