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

Appium behavior change ? Broke all our tests ... #1103

Closed
vitoo opened this issue Jan 9, 2017 · 13 comments
Closed

Appium behavior change ? Broke all our tests ... #1103

vitoo opened this issue Jan 9, 2017 · 13 comments

Comments

@vitoo
Copy link
Contributor

vitoo commented Jan 9, 2017

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 :

image

I've set cerberus_appium_wait_element to 6000

Any idea ?

@bcivel
Copy link
Member

bcivel commented Jan 9, 2017

Hi @vitoo
Does it stop before waiting 6 seconds?
How long does he wait?
Thanks
Benoit

@vitoo
Copy link
Contributor Author

vitoo commented Jan 9, 2017

Here it wait only 500 ms :

image

Still loading when stop :
image

Before it waited 3320 ms :
image

@bcivel
Copy link
Member

bcivel commented Jan 9, 2017

And what is your value for this parameter cerberus_selenium_wait_element?
Thanks

@vitoo
Copy link
Contributor Author

vitoo commented Jan 9, 2017

3500 ms

@vitoo
Copy link
Contributor Author

vitoo commented Jan 9, 2017

Any idea ?

If a fix can avoid me to edit 30 test cases

@abourdon
Copy link
Member

Hi @vitoo,

So this issue could be closed?

Regards,
Aurélien

@abourdon
Copy link
Member

As this is not an issue I think we can close it

@vitoo
Copy link
Contributor Author

vitoo commented Mar 29, 2017

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. 😡
(i'm still on cerberus Cerberus1.1.10.1-1048)

@vertigo17
Copy link
Member

Does not seems to be acceptable.
Let's reopen until we find a good solution (even if it takes time).

@vertigo17 vertigo17 reopened this Mar 29, 2017
@abourdon
Copy link
Member

Ok I was not aware about regression

@bcivel
Copy link
Member

bcivel commented Mar 29, 2017

linked to appium/java-client#574

@vertigo17
Copy link
Member

@vitoo , can you confirm if with latest version of Cerberus (3.0 integrate the latest version of Appium) it fix the issue ?

@vitoo
Copy link
Contributor Author

vitoo commented Jan 30, 2018

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 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants