Java Selenium 3.141.59-网上驱动器时机，等待驱动程序服务器启动

Question

我知道有关堆栈溢出的此问题有很多类似的帖子。 （ link ， link ， link 等），但它们似乎都没有解决我的问题；在其中，我将Chromedriver版本更新为我正在使用的最新Chrome版本，但似乎根本没有启动 /打开Chrome。谁能建议我做错的事情？

• Chrome版本： 103.0.5060.114（官方构建）（64位）（同类：稳定）
• Chromedriver版本： Chromedriver 103.0.5060.53（https://chromedriver.storage.storage.googleapis.com.com.com.com.com.com/index.html?pathml?pathml?pthml?pthml?ptherj。 = 103.0.5060.53/）
• java硒版（通过maven）： 3.141.59

代码：

logger.info("*** Chrome Simulation(): default viewport");
String exePath = System.getProperty(USER_DIR) + "\\src\\main\\resources\\chromedriver.exe";

System.setProperty("webdriver.chrome.driver", exePath);
ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.addArguments("--start-maximized");

// chromeOptions.addArguments("--headless");
// chromeOptions.addArguments("--disable-gpu");
// chromeOptions.addArguments("--window-size=1920,1080");

driver = new ChromeDriver(chromeOptions);

driver.get(browserMeta.getProperties().getProperty(DESKTOP_URL));

我尝试使用maven命令运行代码时：

mvn test "-Dcucumber.options=--tags '@Test'" -Denv=t1 -Dopenreport=false -DforkCount=0 -DreuseForks=false

启动执行，但我会收到以下错误消息/ stacktrace：

Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: '[REDACTED FOR SAFETY REASONS]', ip: '[REDACTED FOR SAFETY REASONS]', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_161'
Driver info: driver.version: ChromeDriver

org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:202)
org.openqa.selenium.remote.service.DriverService.start(DriverService.java:188)
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:79)
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:213)
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:131)
org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:181)
org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:168)
org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:157)
[MY-ORG-PATH](MyFile:MyLineNumber)
[MY-ORG-PATH](MyFile:MyLineNumber)
[MY-ORG-PATH](MyFile:MyLineNumber)
[MY-ORG-PATH](MyFile:MyLineNumber)
sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
io.cucumber.java.Invoker.doInvoke(Invoker.java:66)
io.cucumber.java.Invoker.invoke(Invoker.java:24)
io.cucumber.java.AbstractGlueDefinition.invokeMethod(AbstractGlueDefinition.java:47)
io.cucumber.java.JavaHookDefinition.execute(JavaHookDefinition.java:59)
io.cucumber.core.runner.CoreHookDefinition.execute(CoreHookDefinition.java:46)
io.cucumber.core.runner.HookDefinitionMatch.runStep(HookDefinitionMatch.java:21)
io.cucumber.core.runner.ExecutionMode$1.execute(ExecutionMode.java:10)
io.cucumber.core.runner.TestStep.executeStep(TestStep.java:92)
io.cucumber.core.runner.TestStep.run(TestStep.java:64)
io.cucumber.core.runner.TestCase.run(TestCase.java:98)
io.cucumber.core.runner.Runner.runPickle(Runner.java:71)
io.cucumber.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:151)
io.cucumber.junit.FeatureRunner.runChild(FeatureRunner.java:135)
io.cucumber.junit.FeatureRunner.runChild(FeatureRunner.java:27)
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
io.cucumber.junit.Cucumber.runChild(Cucumber.java:199)
io.cucumber.junit.Cucumber.runChild(Cucumber.java:90)
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
io.cucumber.junit.Cucumber$RunCucumber.evaluate(Cucumber.java:234)
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
org.apache.maven.surefire.api.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:167)
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:161)
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:84)
org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:87)
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1295)
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:1159)
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:932)
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
org.codehaus.classworlds.Launcher.main(Launcher.java:47)

Answer 1

从 @ @selenium房间的聊天中，我设法使它正常工作；但这不仅是我必须升级的硒。我的pom.xml文件的一部分是相互关联的，我还必须升级以下元素。我也使用的是：

• Cucumber-Java至v7.3.3
• Cucumber-Junit至v7.3.3
• Commons-io至v2.11.0
• Cucumber-Core至v7.3.3

，一旦我升级了这些；该解决方案如前所述。

Answer 2

此错误消息...

Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: '[REDACTED FOR SAFETY REASONS]', ip: '[REDACTED FOR SAFETY REASONS]', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_161'
Driver info: driver.version: ChromeDriver

...表示程序的时间安排等待 chromedriver 开始/启动/启动/spawn em>浏览上下文 ie google-chrome 会话。

您的主要问题是不兼容在您使用的二进制文件之间，如下所示：

• 尽管您正在使用 chrome = 103.0.5060.114 和< em> chromedriver = 103.0.5060.53 with selenium = 3.141.59
• /code> ，古老而古老。

---

解决方案

确保：

• jdk 升级到当前级别 JDK 8U331 。
• Selenium 升级到当前发布强> 。
• ChromeDriver 已更新为当前级别。
• Chrome浏览器已更新为Current Chrome = 103.0 （按照 chromedriver = 103.0.5060.53释放注释）。