You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically while trying to upgrade gems the all method from rspec-expectations in aruba clashes with capybara's definition of all and hence the tests and upgrade fail. I've created a small reproduction repo here: https://github.com/PragTob/all_conflict
✅ What did you expect to see?
I'd wish to be able to use aruba and capybara in the same project, although I acknowledge it's a minority use case
@PragTob just to summarize, the problem is that aruba requires rspec-expectations, and that causes problems in the simplecov test suite because that test suite also requires capybara, and capybara's all conflicts with rspec-expectations' all?
@PragTob looking at your original upgrading pull request (simplecov-ruby/simplecov#1088), it looks like both rspec-expectations and capybara were already present and apparently not conflicting before the upgrade. So this used to actually work.
@mvz yea it used to work, it seems there is a workaround at capybara as detailed: teamcapybara/capybara#2761 - but out of the box it still breaks (see the reproduction repo) but the maintainer there was unresponsive. I wanted to get back to it and see if I can get their workaround to work there as well. My assumption right now is there is a workaround, but capybara doesn't load it when in the cucumber environment (as it does not expect rspec-expectations inside of cucumber).
Any way, looks like the fix then is most likely over at capybara (as there already is a workaround from them) and so likely nothing to do over here :)
I'd keep it open until it's really figured out though.
👓 What did you see?
Basically while trying to upgrade gems the all method from rspec-expectations in aruba clashes with capybara's definition of
all
and hence the tests and upgrade fail. I've created a small reproduction repo here: https://github.com/PragTob/all_conflict✅ What did you expect to see?
I'd wish to be able to use aruba and capybara in the same project, although I acknowledge it's a minority use case
📦 Which tool/library version are you using?
Check the Gemfile.lock from the repro repo: https://github.com/PragTob/all_conflict/blob/main/Gemfile.lock
Should all be most recent
🔬 How could we reproduce it?
Check the repro repo :) https://github.com/PragTob/all_conflict/
📚 Any additional context?
Thanks for all your work! :green
Cross reference, capybare issue: teamcapybara/capybara#2761
The text was updated successfully, but these errors were encountered: