search

michaelklishin / cucumber.el

Emacs mode for editing Cucumber plain text stories
None!
253 stars 90 forks source link

make the execution command customizable and not bound to rake #15

Closed senny closed 13 years ago

senny commented 13 years ago

We don't use rake in our projects and we want to run cucumber directly or via bundle exec. I added support for a custom execution command:

(defcustom feature-cucumber-command 
"rake cucumber CUCUMBER_OPTS=\"{options}\" FEATURE=\"  {feature}\""
"set this variable to the command, which should be used to execute cucumber scenarios."

I left rake as the default, so nothing should change for current users but it's now possible to specify a different execution command like so:

(setq feature-cucumber-command "bundle exec cucumber {feature}")

I had to add the variable feature-default-directory to get the rake execution working for feature-verify-all-scenarios-in-project so that it passes features as the FEATURE="" argument, which in turns runs everything.

Cheers, -- Yves

michaelklishin commented 13 years ago

Thank you!