Skip to content
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

SitePrism does not delegate Capybara in-built matchers to root_element (3.30 bug) #62

Closed
luke-hill opened this issue Jun 26, 2020 · 3 comments
Labels
Bug Fix Something isn't working Needs Investigation Further information is required to act on this

Comments

@luke-hill
Copy link
Collaborator

Issue to raise for SitePrism framework

When running capybara matchers, the current_scope failure is only triggered for have_link. have_text seems to be fine. Maybe worth investigating more.

@tgaff - This is the 3.30 bug we found with capybara.

Environment

  • N/A

Expected Behavior

test runs

Actual Behavior

current_scope failure

Steps to reproduce

use have_link on site_prism 3.42 with capybara > 3.30

@luke-hill luke-hill added Bug Fix Something isn't working Needs Investigation Further information is required to act on this labels Jun 26, 2020
@HashNotAdam
Copy link
Contributor

I'm unable to reproduce this in SitePrism 3.6
The old version of Capybara is causing me issues so, if this is still an issue, I'd like to help get it fixed

@luke-hill
Copy link
Collaborator Author

@HashNotAdam This is now 60-70% fixed. The next version of site_prism will unlock capybara restrictions.

@luke-hill
Copy link
Collaborator Author

This is now fixed in master and will be released in v3.7 shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Fix Something isn't working Needs Investigation Further information is required to act on this
Projects
None yet
Development

No branches or pull requests

2 participants