Closed GoogleCodeExporter closed 9 years ago
Can you provide me your test case - a small program that can reproduce the
issue?
Original comment by andrewch...@chromium.org
on 27 Dec 2014 at 12:29
The issue is reproducible with the apk, that you can find it in this link:
https://www.dropbox.com/s/iq4xrngeyrlk2ed/Test.apk?dl=0
I automate with appium.
My test case is very simple:
- Load the app, switch to the webview and look for the header with title
"Login". The step is successful. Though the element exists, it's not displayed.
- Try to click on the "Register" link. The element exists, but it's impossible
to click it because it's not displayed.
Original comment by pkott...@gmail.com
on 5 Jan 2015 at 2:28
we are not allow to download any apk or exe code here.
do you have Selenium codes that I can run to reproduce the case?
Original comment by andrewch...@chromium.org
on 22 Jan 2015 at 2:11
What I'm doing in my code is very simple
webDriver.context(contextName);
Where webDriver is AppiumDriver and contextName the webView I want to access.
WebElement webElement = webDriver.findElement(By.xpath(xpath));
webElement.click();
xpath is the locator of the element I want to click.
findElement fails. Nevertheless, I can see and verify this locator in chrome
with Inspect Devices.
I sent you the .apk because we work with Titanium, this is the tool to build
our application. I don't know if the issue occurs also for other hybrid
applications developed with different tools.
Original comment by pkott...@gmail.com
on 22 Jan 2015 at 10:03
your xpath may not correct.
you need provide the code for us to trouble shoot.
Just wrote a test case in Appium, and it ran just fine.
driver.navigate().to("http://selftechy.com/");
//
WebElement webElement = driver.findElement(By.xpath("//div[@id = 'page']/ul/li[3]/a")); // Click work
if (webElement != null)
webElement.click();
> info: --> POST /wd/hub/session/555cc9e3368e6299641436ffb9755de2/url
{"url":"http://selftechy.com/"}
> info: [debug] Proxying command to 127.0.0.1:9515
> info: [debug] Making http request with opts:
{"url":"http://127.0.0.1:9515/wd/hub/session/555cc9e3368e6299641436ffb9755de2/ur
l","method":"POST","json":{"url":"http://selftechy.com/"}}
> info: [debug] Proxied response received with status 200:
{"sessionId":"555cc9e3368e6299641436ffb9755de2","status":0,"value":null}
> info: <-- POST /wd/hub/session/555cc9e3368e6299641436ffb9755de2/url 200
4881.371 ms - 72
> info: --> POST /wd/hub/session/555cc9e3368e6299641436ffb9755de2/element
{"using":"xpath","value":"//div[@id = 'page']/ul/li[3]/a"}
> info: [debug] Proxying command to 127.0.0.1:9515
> info: [debug] Making http request with opts:
{"url":"http://127.0.0.1:9515/wd/hub/session/555cc9e3368e6299641436ffb9755de2/el
ement","method":"POST","json":{"using":"xpath","value":"//div[@id =
'page']/ul/li[3]/a"}}
> info: [debug] Proxied response received with status 200:
{"sessionId":"555cc9e3368e6299641436ffb9755de2","status":0,"value":{"ELEMENT":"0
.3876677581574768-1"}}
> info: <-- POST /wd/hub/session/555cc9e3368e6299641436ffb9755de2/element 200
448.960 ms - 102
> info: --> POST
/wd/hub/session/555cc9e3368e6299641436ffb9755de2/element/0.3876677581574768-1/cl
ick {"id":"0.3876677581574768-1"}
> info: [debug] Proxying command to 127.0.0.1:9515
> info: [debug] Making http request with opts:
{"url":"http://127.0.0.1:9515/wd/hub/session/555cc9e3368e6299641436ffb9755de2/el
ement/0.3876677581574768-1/click","method":"POST","json":{"id":"0.38766775815747
68-1"}}
> info: [debug] Proxied response received with status 200:
{"sessionId":"555cc9e3368e6299641436ffb9755de2","status":0,"value":null}
Original comment by andrewch...@chromium.org
on 22 Jan 2015 at 8:41
Original comment by andrewch...@chromium.org
on 6 Feb 2015 at 1:54
Original comment by samu...@chromium.org
on 21 Feb 2015 at 12:26
Original issue reported on code.google.com by
pkott...@gmail.com
on 22 Dec 2014 at 3:56