Polling interval when using implicit waits?

[Rodrigo Martin]

Hi all, hope you are doing great!

I am trying to find out what is the exact polling time being used in both ios, and android driver implementations, when implicit wait is being used.

Where can I find those values, and also, may those be changed?

Thanks and have a great beginning of the year :)

[Jonathan Lipps]

It's here:

https://github.com/appium/appium/blob/master/lib/devices/common.js#L58

What's not working about it as is?

--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/groups/opt_out.

[Rodrigo Martin]

Thanks a lot, Jonathan.

Nothing's wrong, I'm still working on an appium Proof of Concept for my company, one of the questions was how much time was the driver waiting when implicit waiting. One of our concerns is that the polling takes too much time. 500ms seems good! 

Thanks again, and keep up the good work.

Cheers from Argentina.

[Rodrigo Martin]

It's me again.

Is there an "easy" way to change the default value of 500ms for polling? I see that the method receives a parameter, but I'm not sure if that can be configured without modifying the appium driver.

Thanks and have a good weekend!

[bootstrap online]

I think it uses the implicit wait setting so try modifying that value.

[bootstrap online]

waitMs - configurable via implicit wait.
intervalMs - I don't think you can change this without modifying the
appium server source code.

[Jonathan Lipps]

There's no way to set it right now. If you can think of a good reason to make it configurable, I'm happy to. But only if the argument isn't also just an argument for making a one-time change to the value in the code.

[Rodrigo Martín]

thanks bootstrap, jonathan.

It would be really nice to be able to make it configurable, because we execute the majority of our tests using a cloud service, where each second of usage means $. If we could tweak the polling interval easily, it's gonna be easier to found out the right values for our tests. Another usage would be to change it programatically for executing on an android driver with 250ms and on an IOS driver with 300 ms, for example.

If you multiply 250ms per 1000 tests per each suite execution, it's a lot of time.

Thanks again for your quick answer!

[bootstrap online]

I think 500ms is fine.

[bootstrap online]

Try changing that value locally and measure the speed difference. I'm
not persuaded this will make the test faster.