Comments on: Article: Introducing Behaviour-Driven Development

By: Kerry Buckley - Random musings on life, work and software development. » Testing java code using rspec and jruby

Thu, 21 Dec 2006 13:45:12 +0000

[...] A couple of months ago, Dan North made this comment on the subject of rspec: I’m a big fan of Ruby, and I like some of the ideas behind rspec. However I’ve been working with Niclas Nilsson on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly. [...]

By: When Done means Done - Acceptance Testing using Behaviour Driven Development. at Al Power

Tue, 05 Dec 2006 03:59:52 +0000

[...] Dan showed an example of writing an acceptance test using JBehave (his replacement for JUnit which removed any reference to testing and replaced it with a vocabulary built around verifying behaviour – Behaviour Driven Development). This was something like (roughly from memory – pretty much made up so any errors are mine!): [...]

By: AI3 - Adaptive Information:::

AI3 - Adaptive Information::: — Fri, 17 Nov 2006 16:41:24 +0000

Behavior-driven Development (BDD)…

Getting the Words Right
There has been some laudable progress in test-driven development (TDD), leading to what is now being touted as “behaviour-driven development” (note the English spelling). Two key proponents of this approach have bee…

By: Dan North

Dan North — Sat, 21 Oct 2006 12:15:23 +0000

JBehave is back under active development, with a small team of committers (rather than just me). You can expect to see some point releases in the next few weeks. I'm a big fan of Ruby, and I like some of the ideas behind rspec. However I've been working with Niclas Nilsson on a Ruby port of JBehave called RBehave, which we think conveys the intent of BDD more clearly.

By: Kerry Buckley

Kerry Buckley — Fri, 20 Oct 2006 18:48:35 +0000

Thanks for making the article available – it appeared in the issue of Better Software just before I subscribed, and I’d been looking for it online. Is JBehave still under active development, or have the cool kids all jumped ship to Ruby and the excellent rspec?

Incidentally, I came up with an alternative approach to AgileDox which (IMO) produces more usable output if you have a large class hierarchy:

http://www.kerrybuckley.com/2006/09/25/an-alternative-approach-to-creating-specs-from-junit-tests/