Skip to content

Latest commit

 

History

History
40 lines (24 loc) · 1.67 KB

HACKING.rdoc

File metadata and controls

40 lines (24 loc) · 1.67 KB

Hacking on Cucumber-Rails

If you have a bug-fix or a new feature you want to contribute, please fork on Github and make your own feature branch:

git clone [email protected]:you/cucumber-rails.git
git checkout -b 87-add-chinese-translation

The feature branch should contain a ticket number (if applicable) and a descriptive name that aligns with the ticket name.

Setting up your environment

Before you change anything, you should make sure you can run all the Cucumber features for Cucumber-Rails. The first time you clone the repo you may have to install Rails for all of the Ruby versions we’re testing against. For this you need RVM:

Installing rubies with RVM

sudo gem install rvm
rvm install 1.8.7 1.9.1

The recommended way to install RVM is from the Git repository. See here for details: rvm.beginrescueend.com/rvm/install/

Installing gems

In order to avoid conflicts we’ll use RVM’s gem sets to set up a gem set for each combination of Ruby version and Rails version to be tested against. Open rvm.yml and modify the rubies section if you have different patchlevels for the rubies.

Installing the various gem sets is done with the following command:

rake rvm:install_gems

This will take 10-15 minutes to complete, as there are many gems to download. After you have done this once you shouldn’t have to do it again (unless future versions require new gems).

If you’ve made changes to the cucumber-rails source and want to re-install it into the RVM environments, you can run:

rake rvm:install_cucumber_rails

Gotchas