Aslak Hellesøy wrote:
I use mkdir and touch.
Me too
Yeah, "mkdir -p features/support && mkdir -p features/step_defnintions
&& touch features/support/env.rb" is really all you need.
However, for new projects I really like to use jeweler to bootstrap all
the setup for Cucumber, RSpec, Rakefiles, etc... With jeweler you just
say "jeweler cool_gem --cucumber --rspec" and all of this gets generated
for you:
create .gitignore
create Rakefile
create LICENSE
create README.rdoc
create .document
create lib
create lib/cool_gem.rb
create spec
create spec/spec_helper.rb
create spec/cool_gem_spec.rb
create features
create features/cool_gem.feature
create features/support
create features/support/env.rb
create features/step_definitions
create features/step_definitions/cool_gem_steps.rb
Here is jewelers site: http://technicalpickles.github.com/jeweler/
-Ben
On May 1, 11:25 pm, James Byrne <[email protected]> wrote:
Setting up cucumber inside a Rails project is no more difficult than
running script/generate cucumber. But what does one do when working
without Rails at all? How do you generate the features tree and all of
its default files?
--
Posted viahttp://www.ruby-forum.com/.
_______________________________________________
rspec-users mailing list
[email protected]http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rspec-users
