-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible issue with xpath on 2.0.1 #880
Comments
Very odd, I just tried to replicate this, but was not able to. I saw someone on the mailing list who had a similar problem, but I dismissed it as an unrelated. Can you create a repo with just a Gemfile which replicates this issue? |
I wasn't able to replicate it in a fresh repository. I did notice during this process that I had a dependency of @ngauthier's domino gem in my development group, which depends on Capybara. I moved it into the test group, re-bundled, and everything was fixed. I'm closing this issue; if anyone else comes across problem this I recommend triple-checking your |
Same stacktrace after the upgrade. Don't have any other gems which depend on capybara. |
I ran into this problem too. Couldn't reproduce it, though. It went away after I emptied out my gemset and ran bundle install again. |
Same issue. xpath wasn't included as a dependency of capybara. Had to add xpath to my Gemfile manually in order to fix. |
Same here, xpath not getting included. |
I just upgraded to 2.0.1 and got this error when I tried to run tests:
I was able to fix it by explicitly adding xpath to my project's Gemfile but this doesn't seem like the expected behavior
The text was updated successfully, but these errors were encountered: