group :test do
gem 'rspec-rails'
gem 'factory_girl'
gem 'capybara'
gem 'spork'
gem 'shoulda-matchers'
gem 'guard-rspec'
gem 'guard-spork'
gem 'database_cleaner'
gem 'selenium-webdriver'
gem 'capybara-webkit'
end
gemspec
<<EOF
can u reconstruct my issue ??
its essential to bundle to fire up tests directly out of the gem. i think its unacceptable to run acceptance tests ((lol) or others) from a seperate app.
if i use a rails 3.2.x app i got the error>> undefined method mass_assignment_sanitizer= which should be able to neutralize if you comment it out in development.rb. but in my case there is nothing to comment out.
in a rails3.1.3 app the installation rails g dresscode:install finishes fine. but if i do a bundle in $dresscode/bundle it will cancel with >>
Bundler could not find compatible versions for gem "rails": In Gemfile: dresscode (>= 0) ruby depends on rails (~> 3.1.0) ruby
gem 'dc_contactform', :path => 'dc_addons/dc_contactform'
group :test do gem 'rspec-rails' gem 'factory_girl'
gem 'capybara' gem 'spork' gem 'shoulda-matchers'
gem 'guard-rspec' gem 'guard-spork'
gem 'database_cleaner'
gem 'selenium-webdriver'
gem 'capybara-webkit'
end
gemspec
<<EOF
can u reconstruct my issue ??
its essential to bundle to fire up tests directly out of the gem. i think its unacceptable to run acceptance tests ((lol) or others) from a seperate app.
if i use a rails 3.2.x app i got the error>> undefined method mass_assignment_sanitizer= which should be able to neutralize if you comment it out in development.rb. but in my case there is nothing to comment out.
any ideas????