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

Solo waits always before searching text #27

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments
Closed

Solo waits always before searching text #27

GoogleCodeExporter opened this issue Mar 24, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

Hi,
I discover, traversing the source code, that the search text methods always 
wait some time before trying to find the desired text.

This lead to longer tests and most of all (for me), it prevents to measure the 
time elapsed between my dialogs.

Can this be corrected?

Best regards,
Alban.

Original issue reported on code.google.com by alban.so...@gmail.com on 15 Nov 2010 at 10:19

@GoogleCodeExporter
Copy link
Author

Hi Alban,

That is unfortunately required. If it does not wait then it will with high 
probability get hold of a view that is not current and that will lead to 
non-trustworthy results. Waits like that are needed when it comes to UI tests. 
Have to give the views time to initiate and also for the platform to clean up 
used views. 

Original comment by renasr...@gmail.com on 15 Nov 2010 at 10:43

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author

Hi,
Thanks for your answer.

2 propositions:
 - does the use of waitForIdleSync can solve this problem?
 - Can you make the timeout delay configurable?

Alban.

Original comment by alban.so...@gmail.com on 15 Nov 2010 at 12:17

This issue was closed.
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

1 participant