Hi, I’ve finally make all my tests pass in Rails 3 with Capybara.
After removing webrat’s dependency in favor of the new Capybara one, I
expected that bundle install would remove Webrat dependencie.
After a few minutes searching for bundler bugs related to removing
dependencies I’ve tried to uninstall webrat gem. Then I understood that
rspec-rails was depending on it…
Is there any reason for that? If so, couldn’t Rspec use Capybara instead
of Webrat if it is not present? Is it possible to depend on Webrat OR
Capybara in the gem specs?
Thank you all, specially David, for this wonderful piece of software
that is Rspec!
Best regards,
Rodrigo.
Fale com seus amigos de graça com o novo Yahoo! Messenger
On Sat, Jun 19, 2010 at 1:07 PM, Rodrigo Rosenfeld R. [email protected] wrote:
Is there any reason for that? If so, couldn’t Rspec use Capybara instead of
Webrat if it is not present? Is it possible to depend on Webrat OR Capybara
in the gem specs?
Gemspecs don’t allow alternative dependencies.
I have a similar issue with the RiCal gem. It works with either the
activesupport OR tzinfo gems, rather than require either I just
document that it requires one or the other and leave it up to the
user.
activesupport OR tzinfo gems, rather than require either I just
document that it requires one or the other and leave it up to the
user.
Maybe Rspec should keep depending on Webrat instead for allowing easy
installation until Gemspecs support alternative dependencies. It is not
that bad for those using Capybara and maybe Capybara will merge to
Webrat anyway…
Thank you for your information,
Rodrigo.
Fale com seus amigos de graça com o novo Yahoo! Messenger
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.