Prevent Capybara from opening sessions just to close them again

sauce_helper.rb

# Allow browser creation to be turned off when calling the 'browser' method.
# This lets us check if a browser has been created, without creating on in the
# process.  Which is less gross then `instance_variable_get` IMO.
#
# Default of `true` means standard behavior still exists
module SauceBrowserCheck
  def browser allow_creation: true
    if (@browser || allow_creation)
      super()
    else
      nil
    end
  end
end

# Logs when a session is created and destroyed
module LoggingBridge
  def write_to_log messages, call_stack_range
    parallel_id = ENV["TEST_ENV_NUMBER"] || 1
    timestamp = Time.now
    logger = $SAUCE_LOGGER || Logger.new(STDOUT)

    log_lead = "[#{timestamp}] - Thread #{parallel_id}  -"
    log_separator = "============================================="

    logger.debug log_separator

    messages.each { |msg| logger.puts "#{log_lead}  #{msg}" }

    # We want the call stack as it was when the method was called, not when the
    # formatter ran, so take four entries off
    call_stack_range.each do |i|
      j = i + 3
      logger.debug "#{log_lead} called from #{caller[j]}"
    end

    logger.debug log_separator
  end

  def initialize opts={}
    caps = opts[:desired_capabilities]
    super opts

    self.write_to_log(  
      ["Created #{self.session_id}",
      "Named \"#{caps[:name]}\""],
      (3..6))

    return self
  end
  
  def quit
    self.write_to_log(
      ["Quitting #{session_id}"],
      (1..3))
    super
  end
end

class Capybara::Selenium::Driver
  prepend SauceBrowserCheck
end

class Selenium::WebDriver::Remote::Bridge
  prepend LoggingBridge
end

Generally it's fine though. It might be nice to see it in a block, but I guess I need to see an actual example as well to decide.