We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some of the Capybara finder options return a generic Capybara::ElementNotFound exception without outputting the options requested.
Capybara::ElementNotFound
This element is visible, but the test expects it to not be visible. @page.main_nav.wait_until(1).not.visible
@page.main_nav.wait_until(1).not.visible
and resulting stacktrace Capybara::ElementNotFound: Unable to find css "#main-nav"
Capybara::ElementNotFound: Unable to find css "#main-nav"
The exception is confusing, because that element is clearly visible on the page when debugging.
Make the exceptions raised more explicit with better messaging.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Some of the Capybara finder options return a generic
Capybara::ElementNotFound
exception without outputting the options requested.This element is visible, but the test expects it to not be visible.
@page.main_nav.wait_until(1).not.visible
and resulting stacktrace
Capybara::ElementNotFound: Unable to find css "#main-nav"
The exception is confusing, because that element is clearly visible on the page when debugging.
Make the exceptions raised more explicit with better messaging.
The text was updated successfully, but these errors were encountered: