Selenium remoteWebDriver:与selenium-standalone-server的连接失败(驱动程序版本未知) [英] Selenium remoteWebDriver : connection to selenium-standalone-server fail (driver version unknown)
问题描述
在用Java编写的应用程序测试中尝试使用remoteWebDriver建立与selenium-server-standalone的连接后，我收到了异常消息.
I received an exception after trying to setup a connection to selenium-server-standalone by using remoteWebDriver in an application test written in Java.
问题与使用remoteWebDriver通过使用Maven启动selenium-server-standalone(使用Xvfb)有关(因为通过不同的会话Xvfb手动运行，然后selenium-server独立运行应用程序测试有效). 该环境由RH Linux R4.1.x，Selenium 2.1，firefox 3.6组成.硒服务器独立测试和应用程序测试都在同一台计算机(虚拟机)上执行.
The issue is related the usage of remoteWebDriver starting selenium-server-standalone (with Xvfb) by using maven (because by running manually by a different session Xvfb and then selenium-server stand alone the application test is working). The environment is composed by RH Linux R4.1.x , Selenium 2.1, firefox 3.6. Both selenium-server-standalone and application test are executed on the same machine (Virtual Machine).
如前所述，如果此实例是通过单独的PUTTY会话(与用于启动应用程序测试的会话分开)启动的，则该应用程序测试将成功连接到selenium-server-standalone-2.21.0实例.以下命令:
As previously said, the application test run successfully connecting to the instance of selenium-server-standalone-2.21.0 if this instance is started by a separate PUTTY session (separate from the one used for starting the application test) with the following commands:
#Xvfb :20 &
#export DISPLAY=:20
#Java –Dwebdriver.firefox.firefox="/opt/firefox/firefox" –jar selenium-server-standalone-2-.21.0.jar -port 4441.
用于连接到selenium-server-standalone的应用程序测试代码如下:
The application test code for connecting to selenium-server-standalone is the following :
DesiredCapabilities capability = DesiredCapabilities.firefox();
capability.setPlatform(Platform.LINUX);
WebDriver driver = new RemoteWebDriver (new URL("http://127.0.0.1:14444/wd/hub"),capability);
driver.manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);
现在尝试在启动应用程序测试之前尝试使用maven单独启动xvfb和selenium-server-stand，我得到以下错误(然后在同一腻子会话中):
Now trying to use maven for starting also xvfb and selenium-server-stand alone before starting the application test I get the following error (then within same putty session):
selenium server conenction string: http://127.0.0.1:14444/wd/hub
brand community file name orig :/opt/optism_svn/trunk/ITests/Projects/core/bbCampaigns/BrandCommunitiesWD/src/test/resources/Orig_BrandCommunity_Test6386.csv
before connecting to web driver
15:17:05.591 INFO - Executing: [new session: {platform=LINUX, browserName=firefox, version=}] at URL: /session)
15:17:05.651 WARN - Exception thrown
java.util.concurrent.ExecutionException: org.openqa.selenium.WebDriverException: java.lang.reflect.InvocationTargetException
Build info: version: '2.2.1', revision: '16551', time: '2012-04-11 21:42:35'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.18-194.el5', java.version: '1.6.0_22'
Driver info: driver.version: unknown
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at org.openqa.selenium.remote.server.DefaultSession.execute(DefaultSession.java:158)
at org.openqa.selenium.remote.server.DefaultSession.<init>(DefaultSession.java:112 )
at org.openqa.selenium.remote.server.DefaultSession.createSession(DefaultSession.java:89)
at org.openqa.selenium.remote.server.DefaultDriverSessions.newSession(DefaultDriverSessions.java:92)
at org.openqa.selenium.remote.server.handler.NewSession.handle(NewSession.java:62)
at org.openqa.selenium.remote.server.rest.ResultConfig.handle(ResultConfig.java:202)
at org.openqa.selenium.remote.server.DriverServlet.handleRequest(DriverServlet.java:597)
at org.openqa.selenium.remote.server.DriverServlet.doPost(DriverServlet.java:548)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.openqa.selenium.remote.server.DriverServlet.service(DriverServlet.java:520)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.openqa.jetty.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.openqa.jetty.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:677)
at org.openqa.jetty.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1530)
at org.openqa.jetty.http.HttpContext.handle(HttpContext.java:1482)
at org.openqa.jetty.http.HttpServer.service(HttpServer.java:909)
at org.openqa.jetty.http.HttpConnection.service(HttpConnection.java:820)
at org.openqa.jetty.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.openqa.jetty.http.HttpConnection.handle(HttpConnection.java:837)
at org.openqa.jetty.http.SocketListener.handleConnection(SocketListener.java:243)
at org.openqa.jetty.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.openqa.jetty.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Caused by: org.openqa.selenium.WebDriverException: java.lang.reflect.InvocationTargetException
Build info: version: '2.2.1', revision: '16551', time: '2012-04-11 21:42:35'
System info: os.name: 'Linux', os.arch: 'amd64', os.version: '2.6.18-194.el5', java.version: '1.6.0_22'
**Driver info: driver.version: unknown**
at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:68)
at org.openqa.selenium.remote.server.DefaultDriverFactory.newInstance(DefaultDriverFactory.java:52)
at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:197)
at org.openqa.selenium.remote.server.DefaultSession$BrowserCreator.call(DefaultSession.java:184)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at org.openqa.selenium.remote.server.DefaultSession$1.run(DefaultSession.java:151)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at org.openqa.selenium.remote.server.DefaultDriverFactory.callConstructor(DefaultDriverFactory.java:58)
... 9 more
**Caused by: java.lang.IllegalStateException: The path to the chromedriver executable must be set by the webdriver.chrome.driver system property**
at com.google.common.base.Preconditions.checkState(Preconditions.java:172)
at org.openqa.selenium.chrome.ChromeDriverService.createDefaultService(ChromeDriverService.java:90)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:107)
... 14 more
**15:17:05.659 WARN - Exception: The path to the chromedriver executable must be set by the webdriver.chrome.driver system property**
用于启动xvfb和selenium服务器的pom.xml是以下文件(与零件相关的xvfb和selenium的摘录):
The pom.xml used for starting xvfb and selenium server is the following one (extract of part related xvfb and selenium) :
<properties>
<!-- Dependencies -->
<selenium-version>2.21.0</selenium-version>
<selenium-plugin-version>2.3</selenium-plugin-version>
<dependency>
<groupId>org.seleniumhq.selenium</groupId>
<artifactId>selenium-java</artifactId>
<version>${selenium-version}</version>
</dependency>
.....
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>selenium-maven-plugin</artifactId>
<version>${selenium-plugin-version}</version>
<configuration>
<background>true</background>
<port>14444</port>
</configuration>
<executions>
<execution>
<id>xvfb</id>
<phase>pre-integration-test</phase>
<goals>
<goal>xvfb</goal>
</goals>
….
<execution>
<id>start-selenium-server</id>
<phase>pre-integration-test</phase>
<goals>
<goal>start-server</goal>
</goals>
</execution>
推荐答案
昨天我遇到了相同的错误:
I had the same error yesterday :
Exception: The path to the chromedriver executable must be set by the webdriver.chrome.driver system property**
我通过在节点计算机的路径中添加chromedriver.exe解决了该问题. ( https://code.google.com/p/chromedriver/downloads/list)但是，如果尝试启动firefox，则会出现此问题很奇怪...
I solved it by adding the chromedriver.exe in the path of the node machine. (https://code.google.com/p/chromedriver/downloads/list) But it's weird to have this problem if try to launch firefox ...
这篇关于Selenium remoteWebDriver:与selenium-standalone-server的连接失败(驱动程序版本未知)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
