Attempt to fix Ferrum timeout errors

docs/CHANGELOG.md

@@ -18,13 +18,17 @@ nav_order: 5
 
     *Alexandre Ignjatovic*
 
+* Improve docs about inline templates interpolation.
+
+    *Hans Lemuet*
+
 * Update generators.md to clarify the way of changing `config.view_component.view_component_path`.
 
     *Shozo Hatta*
 
-* Improve docs about inline templates interpolation
+* Attempt to fix Ferrum timeout errors by creating driver with unique name.
 
-    *Hans Lemuet*
+    *Cameron Dutro*
 
 ## 3.6.0
 

test/sandbox/test/view_component_system_test.rb

@@ -3,7 +3,7 @@
 require "test_helper"
 
 class ViewComponentSystemTest < ViewComponent::SystemTestCase
-  driven_by :cuprite
+  driven_by :vc_cuprite
 
   def test_simple_js_interaction_in_browser_without_layout
     with_rendered_component_path(render_inline(SimpleJavascriptInteractionWithJsIncludedComponent.new)) do |path|

test/test_helper.rb

@@ -40,7 +40,9 @@ def self.warn(message)
 
 require "capybara/cuprite"
 
-Capybara.register_driver(:cuprite) do |app|
+# Rails registers its own driver named "cuprite" which will overwrite the one we
+# register here. Avoid the problem by registering the driver with a distinct name.
+Capybara.register_driver(:vc_cuprite) do |app|
   # Add the process_timeout option to prevent failures due to the browser
   # taking too long to start up.
   Capybara::Cuprite::Driver.new(app, {process_timeout: 60, timeout: 30})