-
Notifications
You must be signed in to change notification settings - Fork 30
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
Fix #205 #207
Fix #205 #207
Conversation
## 4.6.0 | ||
- Spreewald not explicitly depends on Capybara. We don't expect anyone used it without Capybara in the first place. | ||
- Changes to "the ... field should (not) have (an error|the error ...)" step: | ||
- fixed an edgecases where errors were nested deeper inside a .field_with_errors element |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- fixed an edgecases where errors were nested deeper inside a .field_with_errors element | |
- fixed an edgecase where errors were nested deeper inside a .field_with_errors element |
end | ||
|
||
def rails_error? | ||
parent_element_classes = @element.find(:xpath, '..')[:class] &.split(' ') || [] | ||
parent_element_classes.include?('field_with_errors') | ||
has_xpath? do |x| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Brauchen wir dafür noch einen Test?
@kratob Thanks for the PR, I encountered the same issue and the changes reduce the execution time of an affected step from |
…XPath library to construct xpaths
df46cc0
to
06bab5e
Compare
Now released as 4.6.0. |
See #205.
Sped up the
FieldErrorFinder
significantly by setting Capybara.default_max_wait_time to 0. We are always called inside a patiently block anyways.