Comments on: Introducing rbehave

By: emson… » Blog Archive » Understanding RSpec Stories – a Tutorial

Mon, 18 Jan 2010 09:12:45 +0000

[...] Dan North created rbehave which is the Story framework and he describes it as: [...]

By: Open Coding » Behavior-Driven Development with NBehave

Open Coding » Behavior-Driven Development with NBehave — Fri, 11 Dec 2009 07:57:23 +0000

[...] powerful. Here is what its authors say about NBehave: Based on Dan North’s initial vision of rbehave and utilizing the behavioral domain specific language (DSL)of Behavior Driven Design (BDD) we [...]

By: Björn Rochel’s weblog » A new syntax for xUnit.BDDExtensions ???

Björn Rochel’s weblog » A new syntax for xUnit.BDDExtensions ??? — Thu, 27 Nov 2008 13:39:50 +0000

[...] Having said that, here is what I came up with. It’s heavily inspired by MSpec and RBehave. [...]

By: MisBehave 0.1: Oslo’s MGrammar for BDD Executable Specifications

MisBehave 0.1: Oslo’s MGrammar for BDD Executable Specifications — Mon, 10 Nov 2008 01:45:35 +0000

[...] (e.g. a Given step can run an equivalent Given method). The list is growing fast: JBehave, RBehave, NBehave, RSPec, Cucumber, and so on. At InneWorkings, we experimented for a long time with various [...]

By: Dan North

Dan North — Fri, 22 Feb 2008 14:47:07 +0000

Hi Venu.

Thanks for your suggestions. I hope I can help.

Since I wrote this article, RBehave has become the rspec story framework. The rspec team has put a lot of effort into making the story syntax cleaner (you can now specify scenarios as plain text!) and separating out the ruby code. You can also manage different groups of steps separately, which will allow you to do exactly what you are describing with separating out the detail of the scenarios.

You should start using the rspec story framework because I won’t be making any more separate releases of rbehave.