-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Appium behavior change ? Broke all our tests ... #1103
Comments
Hi @vitoo |
And what is your value for this parameter cerberus_selenium_wait_element? |
3500 ms |
Any idea ? If a fix can avoid me to edit 30 test cases |
Hi @vitoo, So this issue could be closed? Regards, |
As this is not an issue I think we can close it |
Hi, I had to edit 30 testcase and add 10 waits per testcase to handle this So to me its a regression, before appium were using the "cerberus_appium_wait_element" ,and now it crash if it takes more than 10 ms to find an element, and i had to set wait in each steps. 😡 |
Does not seems to be acceptable. |
Ok I was not aware about regression |
linked to appium/java-client#574 |
@vitoo , can you confirm if with latest version of Cerberus (3.0 integrate the latest version of Appium) it fix the issue ? |
No i can't (old mission) But i remember this problem was due to the queue change in cerberus, by setting the pool size it fixed this So i think we can closed this issue 😄 |
Hi,
I've updated cerberus to c72c644
Appium android test case are not executed the same way, it looks like now it doesnt wait elements loading before doing an action
So it stop testcase while loading :
I've set cerberus_appium_wait_element to 6000
Any idea ?
The text was updated successfully, but these errors were encountered: