-
Notifications
You must be signed in to change notification settings - Fork 220
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
element.wait_until is broken #408
Comments
I think this is fixed in watir and working properly in page-object. Please reopen if you think there is still a problem. |
I know it's been a while, but, pretty much the same issue: ruby 2.5.5, page-object 2.2.6, watir 6.16.5. I call When debugging into element.wait_until (line 169 of element.rb), the arguments look like this: It seems to me that the call to element.wait_until shouldn't pass a hash, but just be: |
@galinkinlin , what is the issue you are running into? |
Specifically, I am getting the error: However, now that I Iook more closely, I can see that this is only happening for custom elements I've defined, and not everywhere. I must be doing something funky. We were stuck on ruby 1.9.3 until recently, and upgrading everything at once has been quite the chore. |
Nevermind, it's even weirder than that. It works just fine when I run it through Intellij's "Evaluate" console, but not when it runs normally. Whatever is going on has got to be my fault. |
Keep in mind that Page-Object's #wait_until method's arguments are not yet in sync with Watir's - see #471. Page-Object only accepts the positional arguments, it does not yet support keywords or a Hash. |
I am doing a simple some_element.when_visible(20) |
Using Watir 6.0.3, page object 2.0.0 and Ruby 2.1.9
As per latest watir and page-object changes changed below code to
to
but getting
undefined method
zero?' for #Hash:0x4991340 (NoMethodError) `error.however if I get rid of page-object locator shown below Watir 'wait_until'works as expected.
The text was updated successfully, but these errors were encountered: