Setting up rspec-rails for hacking

I am sure most of you could do this easily, but I wanted to write down
how I got there in any case, so here are my instructions on how to set
up rspec-rails to hack on:

Enjoy,
Trevor

Trevor Lalish-Menagh
484.868.6150 mobile
[email protected]

El 07/07/2010, a las 03:54, Lalish-Menagh, Trevor
escribió:

I am sure most of you could do this easily, but I wanted to write down
how I got there in any case, so here are my instructions on how to set
up rspec-rails to hack on:
trevmex's tumblings - How to start hacking a ruby project

Did you know about the rspec-dev meta project?

GitHub - rspec/rspec-dev: RSpec development environment

This is a project which sets up everything you need to do RSpec
development, including hacking on rspec-rails. As long as you have rake
and Bundler (>= 1.0.0.beta) it is quite easy to set-up:

git clone git://github.com/rspec/rspec-dev.git
cd rspec-dev
rake setup # clones all the rspec-* repos under “repos/”
rake # runs all specs and features from rspec-* repos

Perhaps we should update the rspec-* READMEs with a point back to
rspec-dev so that people know about it?

Cheers,
Wincent

Did you know about the rspec-dev meta project?

GitHub - rspec/rspec-dev: RSpec development environment

That is great. I should have looked for that before setting this up. I
just didn’t think about it.

Perhaps we should update the rspec-* READMEs with a point back to rspec-dev so that people know about it?

Good call. That would help.

Thanks,
Trevor

I’ve followed the instructions to install the dev environment, when I
run rake install I get this for the rspec-rails:
cp ./templates/Gemfile ./tmp/example_app/
rake rails:template LOCATION=’…/…/templates/generate_stuff.rb’
(in /Users/garren/webdev/rspec-dev/repos/rspec-rails/tmp/example_app)
generate rspec:install
generate controller wombats index
generate controller welcome index
generate integration_test widgets
generate mailer Notifications signup
generate model thing name:string
generate helper things
generate scaffold widget name:string category:string
instock:boolean
generate observer widget
generate scaffold gadget
run rake db:migrate from “.”
run rake db:test:prepare from “.”
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -I
“/Library/Ruby/Gems/1.8/gems/cucumber-0.8.3/lib:lib” “/Library/Ruby/
Gems/1.8/gems/cucumber-0.8.3/bin/cucumber” --format progress
Using the default profile…
You have already activated rspec-expectations 2.0.0.beta.13, but your
Gemfile requires rspec-expectations 2.0.0.beta.16. Consider using
bundle exec. (Gem::LoadError)

Any ideas on how to fix this?

On Jul 7, 2010, at 5:26 AM, Trevor Lalish-Menagh wrote:

Did you know about the rspec-dev meta project?

GitHub - rspec/rspec-dev: RSpec development environment

That is great. I should have looked for that before setting this up. I just didn’t think about it.

Perhaps we should update the rspec-* READMEs with a point back to rspec-dev so that people know about it?

Good call. That would help.

Done:

Cheers,
David

On Jul 9, 2010, at 8:06 AM, David C. wrote:

That is great. I should have looked for that before setting this up. I just didn’t think about it.
run rake install I get this for the rspec-rails:
generate scaffold widget name:string category:string
Gemfile requires rspec-expectations 2.0.0.beta.16. Consider using
bundle exec. (Gem::LoadError)

Any ideas on how to fix this?

Looks like a change to aruba broke the rspec build :slight_smile: Looking into it now.

It wasn’t aruba. I’m not 100% clear about all this, but I had added
Bundler.setup in a couple of places where it wasn’t necessary, and it
caused trouble. It’s now only in the Rakefiles in each repo and all
appears to be well.

Please give it a shot again and let me know how it’s all working.

Thx,
David

On Jul 9, 2010, at 6:59 AM, garren wrote:

cp ./templates/Gemfile ./tmp/example_app/
instock:boolean
bundle exec. (Gem::LoadError)

Any ideas on how to fix this?

Looks like a change to aruba broke the rspec build :slight_smile: Looking into it
now.

PS - please post at the bottom or inline instead of top-posting:
http://idallen.com/topposting.html