Clarify cuprite driver configuration

Rails is registering a driver called `cuprite`. And when we did that as
well the driver got registered three times somehow. It looked like our
driver options were used in the end but just to clarify I gave it a
unique name.

This was inspired by:

* https://github.com/ViewComponent/view_component/pull/1877

It suggests that it may avoid dead browser errors on CI. We'll see.
This commit is contained in:
Maikel Linke
2023-11-02 14:07:33 +11:00
parent d8cc45c5c3
commit c4c5c97270

View File

@@ -7,7 +7,7 @@ headless = ActiveModel::Type::Boolean.new.cast(ENV.fetch("HEADLESS", true))
browser_options = {}
browser_options["no-sandbox"] = nil if ENV['CI']
Capybara.register_driver(:cuprite) do |app|
Capybara.register_driver(:cuprite_ofn) do |app|
Capybara::Cuprite::Driver.new(
app,
**{
@@ -24,14 +24,14 @@ Capybara.register_driver(:cuprite) do |app|
)
end
# Configure Capybara to use :cuprite driver by default
Capybara.default_driver = Capybara.javascript_driver = :cuprite
# Configure Capybara to use :cuprite_ofn driver by default
Capybara.default_driver = Capybara.javascript_driver = :cuprite_ofn
RSpec.configure do |config|
config.include CupriteHelpers, type: :system
config.include Devise::Test::IntegrationHelpers, type: :system
config.prepend_before(:each, type: :system) { driven_by :cuprite }
config.prepend_before(:each, type: :system) { driven_by :cuprite_ofn }
# Make sure url helpers in mailers use the Capybara server host.
config.around(:each, type: :system) do |example|