Driver wait time is more for negative validation in Appium Studio-10.8.41

#1

When we are executing a script for negative validation of an object, the driver keeps on waiting for 30min trying to find the object in mobile screen. For which I have mentioned the LOG below, where the driver is trying to find the object at 14:59:22 IST and the driver came out of finding the element at 15:32:57 IST. There is driver wait time of 32Min.

Can the driver wait time of 32min can be reduced to some milliseconds for negative validations of objects?

Tool Used- Appium Studio-10.8.41
JAR USED:
appium-client-10.8.41.jar
java-client-4.1.2.jar

LOG:
[Fri May 26 14:59:22 IST 2017] [cc7d] [driver] [start] findElement(By.xpath: //[contains(@text,‘Welcome to’)])
[Fri May 26 14:59:22 IST 2017] [cc7d] [driver] [start] findElementByXPath("//[contains(@text,‘Welcome to’)]")
[Fri May 26 15:32:57 IST 2017] [cc7d] [driver] [end] findElementByXPath
[Fri May 26 15:33:01 IST 2017] [cc7d] [driver] [end] findElement

ERROR:
org.openqa.selenium.NoSuchElementException: org.openqa.selenium.NoSuchElementException: An element could not be located on the page using the given search parameters
For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: ‘2.53.1’, revision: ‘a36b8b1cd5757287168e54b817830adce9b0158d’, time: ‘2016-06-30 19:26:09’
System info: host: ‘EBIII228F1’, ip: ‘172.25.186.92’, os.name: ‘Windows 7’, os.arch: ‘amd64’, os.version: ‘6.1’, java.version: ‘1.8.0_112’
Driver info: driver.version: SeeTestAndroidDriver

#2

Hi, this sounds odd :spy:

can you let us know if you added any code that manages the driver timeouts?

will it be possible to share the server logs during the time of the findElement request?

https://docs.experitest.com/display/AS/Collect+Appium+Studio+Server+side+logs

#3

Hi Tom,
No, No code have been added that manages the driver timeouts.
I have executed my code now and found that the appium studio Driver is waiting for 10 sec by default for a negative validation of an object, if the object is not available on screen.

Mentioned the Log below, where you can see the object is being waited by 10sec by driver for a time out. Cant it be reduced to some 500 milliseconds. ??

[Mon May 29 17:01:35 IST 2017] [54bf] [driver] [start] findElement(By.xpath: //[@id=‘textView_title’])
[Mon May 29 17:01:35 IST 2017] [54bf] [driver] [start] findElementByXPath("//[@id=‘textView_title’]")
[Mon May 29 17:01:45 IST 2017] [54bf] [driver] [end] findElementByXPath
[Mon May 29 17:01:45 IST 2017] [54bf] [driver] [end] findElement

#4

Hi,

You can use driver.getClient().setDefaultTimeout(500)

This will set the timeout waiting for commands to 500

OR

use WebDriverWait (time parameter is in seconds)

new WebDriverWait(driver, 1).until(ExpectedConditions.presenceOfElementLocated(By.xpath("")));

#5

Hi Tom,
By using the below line of code:
driver.getClient().setDefaultTimeout(500)

the driver default wait timeout reduced from 10Sec to 4Sec , mentioned below in the execution log: BUT ITS NOT REDUCING THE DRIVER WAIT TIME TO 500 milliseconds.???

LOG:
[Mon May 29 18:14:09 IST 2017] [1e2b] [driver] [start] findElement(By.xpath: //[@id=‘textView_title’])
[Mon May 29 18:14:09 IST 2017] [1e2b] [driver] [start] findElementByXPath("//[@id=‘textView_title’]")
[Mon May 29 18:14:13 IST 2017] [1e2b] [driver] [end] findElementByXPath
[Mon May 29 18:14:13 IST 2017] [1e2b] [driver] [end] findElement

#6

can you please share with us the server logs during your execution goal?

https://docs.experitest.com/display/public/AS/Collect+Appium+Studio+Server+side+logs