我正试图在docker中使用Selenium chrome运行rspec测试但是发现了几十个错误。最后我将capybara连接到远程水豚，但现在我遇到了这些错误：
得到0次失败和其他2次错误：
1.1) Failure/Error: visit new_user_session_path
Selenium::WebDriver::Error::WebDriverError:
unexpected response, code=404, content-type="text/html"
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Action Controller: Exception caught</title>
....................
Failure/Error: raise Error::WebDriverError, msg
Selenium::WebDriver::Error::WebDriverError:
unexpected response, code=404, content-type="text/html"
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<title>Action Controller: Exception caught</title>
<style>
body {
background-color: #FAFAFA;
...............
所以这是我的 rails_helper.rb 。这真是一团糟，因为我用不同的配置尝试了十几次
require 'simplecov'
SimpleCov.start
ENV['RAILS_ENV'] ||= 'test'
require File.expand_path('../../config/environment', __FILE__)
# Prevent database truncation if the environment is production
abort("The Rails environment is running in production mode!") if Rails.env.production?
require 'spec_helper'
require 'rspec/rails'
require 'turnip/capybara'
require "selenium/webdriver"
require 'capybara-screenshot/rspec'
Dir[Rails.root.join('spec/support/**/*.rb')].each { |f| require f }
Shoulda::Matchers.configure do |config|
config.integrate do |with|
with.test_framework :rspec
with.library :rails
end
end
# Checks for pending migration and applies them before tests are run.
# If you are not using ActiveRecord, you can remove this line.
ActiveRecord::Migration.maintain_test_schema!
Capybara::Screenshot.register_driver(:headless_chrome) do |driver, path|
driver.browser.manage.window.resize_to(1600, 1200)
driver.browser.save_screenshot("tmp/capybara/chrom_#{Time.now}.png")
end
url = 'http://test.prs.com:3001/'
Capybara.javascript_driver = :remote_browser
Capybara.register_driver :headless_chrome do |app|
capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
chromeOqptions: { args: %w(headless disable-gpu no-sandbox) }
)
end
capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
chromeOqptions: { args: %w(headless disable-gpu no-sandbox) }
)
Capybara.default_driver = :remote_browser
Capybara.register_driver :remote_browser do |app|
Capybara::Selenium::Driver.new(app, :browser => :remote, url: url,
desired_capabilities: capabilities)
end
# Capybara::Selenium::Driver.new app,
# browser: :chrome,
# desired_capabilities: capabilities
# end
Capybara.app_host = "http://#{ENV['APP_HOST']}:#{3001}"
Capybara.run_server = false
Capybara.configure do |config|
config.always_include_port = true
end
Chromedriver.set_version '2.32'
# Capybara.javascript_driver = :headless_chrome
# Capybara.server_host= '0.0.0.0'
# Capybara.default_host = "http://test.prs.com"
# Capybara.app_host = "#{Capybara.default_host}:#{Capybara.server_port}"
RSpec.configure do |config|
config.include FactoryGirl::Syntax::Methods
config.include RequestSpecHelper
# Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
config.fixture_path = "#{::Rails.root}/spec/fixtures"
config.before(:each) do
DatabaseCleaner.strategy = :truncation
DatabaseCleaner.clean
end
config.before(:all, type: :request) do
host! 'test.prs.com'
end
config.use_transactional_fixtures = true
config.infer_spec_type_from_file_location!
config.filter_rails_from_backtrace!
end
这是我的docker-compose.yml：
version: '3'
services:
db:
image: postgres
web:
build: .
command: bundle exec rails s -p 3001 -b '0.0.0.0'
volumes:
- .:/prs
ports: ['3000:3000', '3001:3001']
# - "3001:3001"
depends_on:
- db
- selenium
extra_hosts:
- "test.prs.com:127.0.0.1"
environment:
- APP_HOST=test.prs.com
links:
- selenium
selenium:
image: selenium/standalone-chrome-debug:3.6.0-bromine
# Debug version enables VNC ability
ports: ['4444:4444', '5900:5900']
# Bind selenium port & VNC port
volumes:
- /dev/shm:/dev/shm
shm_size: 1024m
privileged: true
container_name: selenium
我对这一切都很陌生，所以任何帮助都会受到赞赏。
答案 0 :(得分：0)
从评论中您已经阐明，您正尝试在selenium docker实例中使用selenium驱动的浏览器时在web docker实例中运行测试。此外，由于您的测试在本地工作，我假设您使用的是Rails 5.1+，因此功能测试的事务测试将起作用。基于这些参数，需要做一些事情才能使一切正常运行。
Capybara需要启动自己的应用程序副本才能运行测试。这是交易测试工作和请求完成检测所必需的。您可以使用
启用它Capybara.run_server = true # You currently have this set to false for some reason
Capybara需要在可以从selenium泊坞窗实例访问的界面上运行其应用程序副本。最简单的方法是指定绑定到0.0.0.0
Capybara.server_host = `0.0.0.0`
Capybara.server_port = 3001 # I'm assuming this is what you want, change to another port and make sure it's reachable from `selenium` instance if desired
驱动程序capybara正在使用需要配置为使用selenium实例
Capybara.register_driver :remote_browser do |app|
capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
chromeOptions: { args: %w(headless disable-gpu no-sandbox) }
)
Capybara::Selenium::Driver.new(app,
:browser => :remote,
url: "http://selenium:4444",
desired_capabilities: capabilities
)
end
Capybara.javascript_driver = :remote_browser
# Capybara.default_driver = :remote_browser # only needed if you want all tests to use selenium rather than just JS tagged tests.
配置Capybara在访问相对URL时使用正确的主机
Capybara.app_host = "http://web:3001" # a URL that represents the `web` docker instance from the perspective of the `selenium` docker instance
注意：如果您希望测试在我猜测的端口3001上运行，那么您希望阻止docker实例在该端口上启动rails s，因为您希望针对应用程序实例运行测试Capybara本身发起# command: bundle exec rails s -p 3001 -b '0.0.0.0'。如果您当前在3001上运行的实例是针对其他内容的，那么您将需要一个不同的端口来进行测试。
此外，如果您未运行Rails 5.1+，那么您需要设置config.use_transactional_fixtures = false并完全配置database_cleaner - https://github.com/DatabaseCleaner/database_cleaner#rspec-with-capybara-example。如果你使用的是Rails 5.1+，那么你可以删除所有的database_cleaner东西。
答案 1 :(得分：0)
我的问题与Docker，Selenium，Capybara，Chromedriver或其他任何东西完全无关。他们都是红鲱鱼，因为在我的容器上，只有与功能规格相关的测试失败了。
事实证明它们都失败了，因为功能规范是应用程序中唯一查看IP地址的部分。
我正在使用ip_anonymizer宝石，但无法为容器设置IP_HASH_SECRET。希望其他与Capybara和CI一起使用此gem的人会发现此功能有用。