Using puma for Capybara tests?

Development
1

As the version bump to Capybara 3.x just went into development, I’d like to discuss about using puma for the Cabybara tests. The is the default for Capybara 3.x, but I did set it to webrick like it was for 2.x. The execution with puma is a bit faster and the only downside I do see is that puma needs to get added to the bundle.

diff --git a/bundler.d/test.rb b/bundler.d/test.rb
index 00ecba0c0..0a5a5b1aa 100644
--- a/bundler.d/test.rb
+++ b/bundler.d/test.rb
@@ -19,4 +19,5 @@ group :test do
   gem 'rfauxfactory', '~> 0.1'
   gem 'robottelo_reporter', '~> 0.1'
   gem 'webmock'
+  gem 'puma'
 end
diff --git a/test/integration_test_helper.rb b/test/integration_test_helper.rb
index fa7a10e94..d716f826d 100644
--- a/test/integration_test_helper.rb
+++ b/test/integration_test_helper.rb
@@ -15,8 +15,6 @@ Minitest::Retry.on_consistent_failure do |klass, test_name|
   Rails.logger.error("DO NOT IGNORE - Consistent failure - #{klass} #{test_name}")
 end
 
-Capybara.server = :webrick
-
 Capybara.register_driver :poltergeist do |app|
   opts = {
     # To enable debugging uncomment `:inspector => true` and
  • Bring puma in
  • Continue to use webrick

0 voters

Show results
2