Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Requirements for usage not fully documented #26

Open
theldoria opened this Issue · 0 comments

1 participant

@theldoria

I found out that the mode uses feature-cucumber-command and thus calls 'rake cucumber' to verify tests by default, but I did'nt find anything in the documentation what the expected task should look like for this.

I know I can customize that variable, but I like to always use the default as much has possible, because commonly you get less trouble with it (it's better testet) and the default are normally well thought through.

For example, my rakefile currently uses the following for feature testing:
require "rake"
require 'cucumber'
require 'cucumber/rake/task'
CUKE_RESULTS = 'results.html'
Cucumber::Rake::Task.new(:features) do |t|
t.cucumber_opts = "features --format html -o #{CUKE_RESULTS} --format pretty --no-source -x"
t.fork = false
end

BTW, the documentation for feature-cucumber-command does not specify how the command should be build. What is {options}, what {feature}, are they required? Does the order matter? I can guess, read lisp code (what I did :-) ) or do a trial-and-error to find out...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.