From: Gernot Hassenpflug <gernot@...049.local>
Date: 2008-10-10T09:57:46+09:00
Subject: Re: integration testing tools? story runner, rbehave, cucumber?

Trans <transfire@gmail.com> writes:

> On Oct 9, 5:22�am, Gernot Hassenpflug <ger...@NOTE049.local> wrote:
>> Dear all,
>>
>> I joined a pretty young VC company a month ago. We are using
>> ruby/merb/datamapper/MySQL, and doing agile development. We use rspec
>> for unit tests. Now we want to start writing integration tests. For this
>> I found out the existence of rbehave (Dan North et al.) and Story Runner
>> (David Chelimsky). I also discovered cucumber as a successor to Story
>> Runner. But I can find very little on rbehave, and its development seems
>> to have stopped in 2006. Is there any concensus on the best tools for
>> integration testing in ruby?
>
> "A few days ago, David Chelimsky announced that RSpec's Story Runner
> now works with the rspec_on_rails plugin. Story Runner is the result
> of Dan North's hard work to merge his rbehave project into RSpec. This
> gives us the ability to write acceptance tests using RSpec's
> expressive expectations. In addition, Story Runner provides a
> structure for your stories (acceptance tests) that helps clearly
> express the assumptions and expectations of your code."
>
> See: http://evang.eli.st/blog/2007/9/1/user-stories-with-rspec-s-story-runner
>
> I must say though, reading over all this stuff, I think you all are
> suffering from an over abundance of time and brain cells --K.I.S.S.
> seems to have become old-fashioned.

Thank you, yes, I found this entry in my searchd but did not notice the
merging of rbehave (mea culpa ...). I'll take a look at the screencast
later. OK, I am happy to use RSpec with its, um, integrated integration
test. 

I also agree on KISS being absent, but I think that with team work, many
"stakeholders", incremental development and gradual concretization of
modules and functionality, things that automate tests (if only for
regression) are very valuable. For instance, we have hudson running
continuous build tests at 5 minute intervals.... the brains I guess
comes from a) implementing a maintanable automatic framework, and b)
writing sane tests.

Best regards, Gernot
Cirius Technologies, Tokyo, Japan