search

FuckTheWorld / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

ImplicitWaitTest fails on Android #998

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement has started failing 
on chrome_beta ever since I upgraded it to 40.0.2214.36. I've tried running 
this test on my own devices with KitKat and Lollipop but can't reproduce the 
failure locally.

========== 
org.openqa.selenium.ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement 
(3.442s)
org.openqa.selenium.NoSuchElementException: no such element
  (Session info: chrome=40.0.2214.36)
  (Driver info: chromedriver=2.12.305787 (e732b712217b2652d6b1f7830d89ae4d49ce7aaf),platform=Linux 3.2.0-55-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 3.01 seconds
For documentation on this error, please visit: 
http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '2.33.0', revision: '4e90c97', time: '2013-11-07 00:32:13'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: 
'3.2.0-55-generic', java.version: '1.7.0_65'
Session ID: 5fe4bc6e9b7e4026074109c2e2ae9dc0
Driver info: org.openqa.selenium.testing.drivers.TestChromeDriver
Capabilities [{platform=ANDROID, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, chrome={}, rotatable=false, locationContextEnabled=true, 
mobileEmulationEnabled=false, version=40.0.2214.36, takesHeapSnapshot=true, 
cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, 
browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, 
applicationCacheEnabled=false, takesScreenshot=true}]
    at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:191)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:307)
    at org.openqa.selenium.remote.RemoteWebDriver.findElementById(RemoteWebDriver.java:348)
    at org.openqa.selenium.By$ById.findElement(By.java:216)
    at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:299)
    at org.openqa.selenium.ImplicitWaitTest.testShouldImplicitlyWaitForASingleElement(ImplicitWaitTest.java:65)
    at org.openqa.selenium.testing.SeleniumTestRunner$2.evaluate(SeleniumTestRunner.java:107)
    at org.openqa.selenium.testing.SeleniumTestRunner.runChild(SeleniumTestRunner.java:80)
    at org.openqa.selenium.testing.ParallelSuite$2.run(ParallelSuite.java:40)
    at org.openqa.selenium.testing.ParallelSuite$ThreadPool$1.run(ParallelSuite.java:79)

Original issue reported on code.google.com by samu...@chromium.org on 10 Dec 2014 at 12:54

GoogleCodeExporter commented 9 years ago 
Issue 1017 has been merged into this issue.

Original comment by samu...@chromium.org on 23 Jan 2015 at 9:47

GoogleCodeExporter commented 9 years ago 
testShouldReturnAfterFirstAttemptToFindManyAfterDisablingImplicitWaits is now 
also failing. Both fail with the following error, when trying to click the 
"adder" button:

org.openqa.selenium.WebDriverException: unknown error: Element is not clickable 
at point (-94, 21)

Neither of the two test failures are reproducible on my Nexus 4.

Original comment by samu...@chromium.org on 23 Jan 2015 at 9:49

GoogleCodeExporter commented 9 years ago 
Just talked to Seva and these tests are passing in the webtesting team's tests. 
Seems like there's something wrong with our infrastructure.

Original comment by samu...@chromium.org on 23 Jan 2015 at 11:28

GoogleCodeExporter commented 9 years ago

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:19