Forum: RSpec [Cucumber] [Ann] Salad, aka Multi-instance Cucumber

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Bart Z. (Guest)
on 2009-05-20 16:55
(Received via mailing list)
(Apologies for crossposting)

Yesterday, my pair and I wrote a rough rake task to run features
against multiple instances of Cucumber. We decided to call it Salad,
since multiple cucumbers makes a nice salad :). The script is very
rough, and scratches mostly our own itch. The rake task itself can be
found at http://gist.github.com/114709.

On a 8-core Mac Pro running with 8 instances, we see a speed increase
of roughly 75%, reducing running time of our entire suite from ~7m30s
to ~2m30s. We've only tested this script on Mac OS X 10.5.

Basic flow is this:
- Create n extra test databases, similar to the test database in
config/database.yml
- Split all features evenly in n feature "groups"
- Fork n Cucumber processes, and let them run their designated feature
groups

We both are neither Cucumber internal experts, nor Ruby experts, so
this could use a lot of work. I personally would love to have this all
as a command line option to cucumber itself.

Two major caveats:
- You need to explicitly set RAILS_ENV to 'test'. We couldn't find an
easy way to force this env from within the rake task
- The project we used to test this all on has some random failures on
specific features with this rake task, whereas rake features doesn't
report any failures at all. This could probably have something to do
with either transactional fixtures or some sort of memory leaks. We
found it happens more frequent when using more instances of cucumber.

So, try it out from http://gist.github.com/114709, and post your
findings!

cheers,
bartz
This topic is locked and can not be replied to.