Comments on: Why Behavior Driven Development is good

By: TDD Boot Camp - Comprehensive Test-Driven Development Training in .NET – Software development is a series of translations

Thu, 28 Jan 2010 02:46:38 +0000

[...] is how you do behavior driven development. We took our acceptance criteria and wrote them out as code in the form of unit tests. These unit [...]

By: Andreas

Andreas — Tue, 05 Jan 2010 09:13:19 +0000

Hello, just wanted to say thanks for this post, I go back and refer to it every other day. :) It’s the one article that made BDD click for me. Thank you!

By: Jon Kruger’s Blog » Software development is a series of translations

Jon Kruger’s Blog » Software development is a series of translations — Fri, 02 Oct 2009 11:57:30 +0000

[...] is how you do behavior driven development. We took our acceptance criteria and wrote them out as code in the form of unit tests. These unit [...]

By: Jon Kruger’s Blog » Blog Archive » Unit Testing JavaScript - Introduction, JavaScript basics

Tue, 25 Nov 2008 23:50:43 +0000

[...] Why Behavior Driven Development is good [...]

By: Justin Kohnen

Justin Kohnen — Mon, 28 Jul 2008 19:39:38 +0000

Jon-

Great post. It answered a few questions I had about BDD. Keep em coming.

By: Tim

Tim — Sun, 27 Jul 2008 16:06:12 +0000

Jon, I couldn’t agree more with your points here. Just shifting the syntax of my tests to use the BDD wording is what pushed me over the top on gettng TDD through my head. Suddenly, what I was doing made so much sense, and it’s just snowballed from there. Thankfully.

A word of caution, though is using the two terms totally interchangeably. Given the inability to get all the way into the code base of .Net, we’ll likely never achieve full on BDD in our environment. This is Bellware’s (via Steve Harman) BDD v. bdd argument. What we’re doing here is bdd…and when we shift to writing Ruby we’ll go for full on BDD. :)