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.

at the line “Then my savings account balance should be $80″
I changed it to “Then my savings account balance should be $85″

then both the scenarios fail and the result is as shown below

Running 2 scenarios:
FF

2 scenarios: 0 succeeded, 2 failed, 0 pending

FAILURES:
1) transfer to cash account (savings account is in credit) FAILED
Spec::Expectations::ExpectationNotMetError: expected: 85,
got: 80 (using ==)
e.rb:39:in `my savings account balance should be’
e.rb:38
e.rb:24

2) transfer to cash account (savings account is overdrawn) FAILED
RBehave::UnknownStepException: my cash account balance should be
e.rb:51
e.rb:24

I expected the 2nd test to pass, and it is giving a Unknown Step Exception. Is this a bug ??

I have one more suggestion. Is there any way we can make the scenario where we put in the logic as a more generalized one with appropirate ruby code, and keep the other set of scenarios as written by a business analyst, as separate set.