1
Vote

IP information should be display on driver

description

Currently IP information is not displaying. It should display Ip information on header so that can map IP to respective url.

file attachments

comments

innffinnitty wrote Feb 4, 2015 at 9:32 AM

Hello,

There are issues using the project on Emulator 8.1. First, there is an error saying "Cannot deploy app: Invalid target device specified". If I deploy the WindowsPhoneDriver.xap via Visual Studio to the Emulator, I am not able to see any IP address, no URL, just a blank white screen.

Any poposals how shall I continue further?

vjrantal wrote Feb 4, 2015 at 11:05 AM

You could try an experimental release from https://winphonewebdriver.codeplex.com/releases/view/611322 that might work better. With this release, please install the XAP to device / emulator as you would install any other XAP file and do not use the custom deployment tool that is a part of this project's source tree.

asthanarht wrote Feb 4, 2015 at 7:19 PM

@Innfinitty - Try what Vj is suggesting. There is no problem in windows 8.1 . Give me more log so that we can identify issue.

innffinnitty wrote Feb 9, 2015 at 8:13 AM

Hello,

I have deployed "WindowsPhoneDriver_Experimental_Release.xap" to the Windows Phone 8.1 Emulator. When I open it and go to the settings, I see "Emulator network interface" is 169.254.80.80 and "port" 8080. If I write my simple test code like this:

public class Test {
public static void main(String[] args) throws MalformedURLException {
    DesiredCapabilities desiredCapabilities = DesiredCapabilities.internetExplorer();
    RemoteWebDriver driver = new RemoteWebDriver(new URL("http://169.254.80.80:8080/wd/hub"), desiredCapabilities);
    driver.get("http://www.google.com");
}
}

I get the following error:

Exception in thread "main" org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure.
Driver info: driver.version: RemoteWebDriver
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:593)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)
at com.sap.webdriver.fw.Test.main(Test.java:14)
Caused by: org.apache.http.conn.HttpHostConnectException: Connect to 169.254.80.80:8080 [/169.254.80.80] failed: Connection timed out: connect
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at org.openqa.selenium.remote.HttpCommandExecutor.fallBackExecute(HttpCommandExecutor.java:215)
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:184)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:572)
... 4 more
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117)
... 16 more

innffinnitty wrote Feb 9, 2015 at 8:14 AM

Here are the setting of the Emulator.

innffinnitty wrote Feb 9, 2015 at 8:24 AM

And, if I try to write

RemoteWebDriver driver = new RemoteWebDriver(new URL("http://10.55.86.240:8080/status"), desiredCapabilities);

instead of

RemoteWebDriver driver = new RemoteWebDriver(new URL("http://169.254.80.80:8080/wd/hub"), desiredCapabilities);

I have the following message:

Exception in thread "main" org.openqa.selenium.WebDriverException: Sorry, not implemented yet.
Command duration or timeout: 350 milliseconds
Driver info: org.openqa.selenium.remote.RemoteWebDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:153)

innffinnitty wrote Feb 9, 2015 at 9:10 AM

Hey guys,

I found that you are not supporting /wd/hub, so I changed the code like this:
public static void main(String[] args) throws MalformedURLException {
    DesiredCapabilities desiredCapabilities = DesiredCapabilities.internetExplorer();
    RemoteWebDriver driver = new RemoteWebDriver(new URL("http://10.55.86.240:8080"), desiredCapabilities);
    driver.navigate().to("http://codeplex.com");
    System.out.print("I can see its working and dont complain me");
}
So, the WebDriver has loaded the Internet Explorer and the eclipse returned me the expected "I can see its working and dont complain me" but the IE says "We are having trouble displaying this page". I have checked that I cannot access any web page via the emulator, so I guess that this is my issue now, right?

vjrantal wrote Feb 9, 2015 at 10:03 AM

Yes, the remote driver should be configured against http://169.254.80.80:8080 and not http://169.254.80.80:8080/wd/hub .

If you meant that you can't access any Web pages (like http://codeplex.com ) even manually with the IE browser found from your emulator, sounds like network connectivity in general is indeed your issue.

innffinnitty wrote Feb 9, 2015 at 12:02 PM

Hi guys,

I'd like to thank you! I fixed the issues with the emulator thanks to you and also, I have configured the Internet and LAN settings using the following support page: https://msdn.microsoft.com/library/windows/apps/ff754351(v=vs.105).aspx
The issue was that my LAN Settings in Internet options had to be bypassed for certain proxy and also, the ip4v settings we using static IP. Now everything is running perfectly fine :)

THANK YOU once again!