hkxgzxt1987 / nativedriver

Automatically exported from code.google.com/p/nativedriver
Apache License 2.0
0 stars 0 forks source link

implicitlyWait not working properly for AndroidNativeDriver #18

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. _phone = new AndroidNativeDriverBuilder().withDefaultServer().build();
2. _phone.manage().timeouts().implicitlyWait(10000, TimeUnit.MILLISECONDS);
3. _phone.findElement(AndroidNativeBy.text("Pluto"));  // doesn't exits

What is the expected output? What do you see instead?
The test should take about 10 seconds, but takes more than a minute.

What version of the product are you using? On what operating system?
SVN trunk from 17.02.2012. Android 2.2 (API level 8).

Please provide any additional information below.
The problem occurs both on the device and the emulator. On the iPhone, it works 
fine.
Here are some results: 1000ms (timeout) ==> 24.3s (duration), 100ms ==> 22.1s, 
10ms ==> 2.7s.

Original issue reported on code.google.com by pfark...@gmail.com on 17 Feb 2012 at 2:24

GoogleCodeExporter commented 8 years ago
I faced same issue and I found the reason at
https://groups.google.com/forum/#!msg/nativedriver-users/nTSiHFXcNGY/44bi2lqhbzw
J

Please use system clock instead process clock.

Original comment by matsuyam...@dena.jp on 11 Dec 2012 at 8:18