简体   繁体   English

尝试在Chrome v54.0.2810.98和Selenium Webdriver 2.53.0上启动Selenium测试时打开空白页

[英]Blank page opened when trying to start a Selenium test on Chrome v54.0.2810.98 and Selenium webdriver 2.53.0

I am trying to Start a Selenium test in Chrome but I am only seeing a blank page. 我正在尝试在Chrome中启动Selenium测试,但只看到一个空白页。 This only started happening after updating to the version 54.0.2810.98 (64-bit) of Chrome. 这只有在更新到Chrome 54.0.2810.98(64位)版本后才开始发生。

This is the version of watir-webdriver I am using: 0.7.0.8. 这是我使用的watir-webdriver版本: 0.7.0.8.

OS Version:  10.11.6, El Capitan

My questions are: 我的问题是:

Does my combination of watir-webdriver, selenium-webdriver work with the latest version of Chrome? 我的watir-webdriver,selenium-webdriver组合可以与最新版本的Chrome一起使用吗?

If it does, what do i need to do to get it running again? 如果可以,我该怎么做才能使其再次运行?

If not, do I need to update to Selenium3? 如果没有,我是否需要更新到Selenium3?

Here is the stack trace: 这是堆栈跟踪:

Minitest::UnexpectedError: Errno::ECONNREFUSED: Connection refused - connect(2)
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `initialize'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `open'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `block in connect'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/timeout.rb:69:in `timeout'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/timeout.rb:100:in `timeout'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `connect'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:756:in `do_start'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:745:in `start'
    /Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:1285:in `request'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/default.rb:107:in `response_for'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/default.rb:58:in `request'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/common.rb:59:in `call'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:649:in `raw_execute'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:627:in `execute'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:238:in `getWindowHandles'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/target_locator.rb:75:in `ensure in window'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/target_locator.rb:78:in `window'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/watir-webdriver-0.7.0.8/lib/watir-webdriver/window.rb:193:in `use'
    /Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/watir-webdriver-0.7.0.8/lib/watir-webdriver/window.rb:96:in `maximize'
    /Users/nickbrill/sportngin/selenium-finance/test/utilities/selenium_utilities.rb:44:in `start_selenium'
    /Users/nickbrill/sportngin/selenium-finance/test/base_test.rb:12:in `setup'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `initialize'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `open'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `block in connect'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/timeout.rb:69:in `timeout'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/timeout.rb:100:in `timeout'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:763:in `connect'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:756:in `do_start'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:745:in `start'
/Users/nickbrill/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/net/http.rb:1285:in `request'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/default.rb:107:in `response_for'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/default.rb:58:in `request'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/http/common.rb:59:in `call'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:649:in `raw_execute'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:627:in `execute'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/remote/bridge.rb:238:in `getWindowHandles'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/target_locator.rb:75:in `ensure in window'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/selenium-webdriver-2.53.0/lib/selenium/webdriver/common/target_locator.rb:78:in `window'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/watir-webdriver-0.7.0.8/lib/watir-webdriver/window.rb:193:in `use'
/Users/nickbrill/.rvm/gems/ruby-1.9.3-p551@selenium-finance/gems/watir-webdriver-0.7.0.8/lib/watir-webdriver/window.rb:96:in `maximize'

运行rm -rf ~/.chromedriver-helper解决了此问题。

The answer to your question is yes. 您的问题的答案是肯定的。

Like Justin suggested, the most important factor is keeping chromedriver version matched with Chrome browser version. 就像Justin建议的那样,最重要的因素是使chromedriver版本与Chrome浏览器版本保持一致。

Beyond that, the latest of everything provides a number of benefits. 除此之外,最新的功能还提供许多好处。 watir-webdriver is deprecated in favor of Watir 6.0, which requires selenium 3, which requires updating to at least ruby 2.0, but ideally to a supported version of ruby. 不建议使用watir-webdriver来支持Watir 6.0,因为Watir 6.0需要硒3,硒至少需要更新为ruby 2.0,但理想情况下需要更新为受支持的ruby版本。 :-) :-)

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Net :: ReadTimeout:Net :: ReadTimeout和Selenium :: WebDriver :: Error :: UnknownError:未知错误:Chrome无法启动Rails 5.1.beta系统测试 - Net::ReadTimeout: Net::ReadTimeout and Selenium::WebDriver::Error::UnknownError: unknown error: Chrome failed to start on Rails 5.1.beta System Test Selenium Webdriver Zoom with Ruby for Chrome - Selenium webdriver zoom with Ruby for Chrome 使Selenium WebDriver在RSpec / Rails中使用Chrome - Getting Selenium WebDriver to use Chrome in RSpec/Rails 如何访问 cookies(Capybara/Selenium Chrome Webdriver) - How to access cookies (Capybara/Selenium Chrome Webdriver) Selenium::WebDriver::Error::UnknownError: 未知错误: Chrome 启动失败: 异常退出 - Selenium::WebDriver::Error::UnknownError: unknown error: Chrome failed to start: exited abnormally 会话未创建例外:使用Selenium Webdriver和Chrome时,Chrome版本必须> = xyz - Session not created exception: Chrome version must be >= x.y.z when using Selenium Webdriver with Chrome Ruby Selenium Webdriver测试脚本(需要建议) - Ruby Selenium Webdriver test script (need advice) 如何修复 WSL2 中的“Selenium::WebDriver::Error::WebDriverError: chrome notreachable” - How to fix "Selenium::WebDriver::Error::WebDriverError: chrome not reachable" in WSL2 水豚/硒浏览器刷新为空白页 - Capybara/selenium browser refreshed with the blank page selenium webdriver打开两页,但在空白页上进行测试 - selenium webdriver opens two pages, but tests on the empty page
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM