I am trying to get this working with phantomjs, I am using:

browser = Watir::Browser.new :phantomjs

when I run a single test file, this starts up phantomjs, but I get a timeout error for every test:

Timeout::Error: execution expired

When I try accessing a site via phantomjs in the rails console it works fine and is very fast. Any idea what this could be?

Can we have mime-types dependency not as strict?

Now it's gem.add_dependency "mime-types", "~> 1.16"

But modern mail gem has the dependency as >= 1.16, < 3, can we have the same here?

require 'watir'
require 'webdrivers'
browser = Watir::Browser.new :firefox

Results in:

Traceback (most recent call last):
        2: from (irb):4
        1: from (irb):4:in `new'
NameError (uninitialized constant Watir::VERSION)

I'm not sure what I'm doing wrong, but it all seems to work when I use gem watir rather than this rails integration.

I would try your gem to test Watir lib, I add "gem 'watir-rails'" to my gem file, do bundle install
and start app on route with this action controller 👍

def index
browser = Watir::Browser.new
browser.goto 'http://www.googe.com'
end

but it send timeout error : "Rails Rack application timed out during boot"

what's wrong?

I d tried to debug something and tried to rewrite some stuff in Watir::Rails and found out that rails-2.x still supported, so I tried to actually check if it works.

Long story short: Rails-2.3.18 cannot run on ruby >= 2.2 since it uses Config::CONFIG which is

irb(main):001:0> Config
(irb):1:in `irb_binding': Use RbConfig instead of obsolete and deprecated Config.
=> RbConfig::Obsolete

on ruby-2.1.10 and dropped in ruby-2.2.

On ruby-2.1.10 we have another issue: rubygems doesn't work:

gem install bundler
ERROR:  Could not find a valid gem 'bundler' (>= 0), here is why:
          Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=error: certificate verify failed (https://api.rubygems.org/latest_specs.4.8.gz)

It was compiled with openssl-1.0.2u and ruby-2.2 with the same version works fine, I assume that ruby-2.1 openssl module lacks current ciphers.

So the question is: can Rails-2.x be dropped in order to simplify some stuff? Same question goes for rails-3, but I haven't tried to boot it yet.

Has anyone implemented this using cucumber-rails or just cucumber?

Hi, I'm trying to use watir-rails with Rails 7.0.6, watir 7.2.2, watir-rails 2.3.0, and watir-rspec 5.0.0.

I was getting this error every time:

Rails Rack application timed out during boot

I did some troubleshooting and found that the application was booting, but the __identify__ middleware was returning a different object_id for @app.object_id. It was not getting called twice, so I'm guessing this is a thread-safety issue. I'm not entirely sure why, but while debugging I found that the problem went away if @app.object_id was accessed after creating the app. My initial changes were printing the object id, but the following change caused it to all work again.

I apologize for the issue without a full reproduction, but I thought I would report this in case anyone else is running in to it.

This is the change that works for me:

--- a/lib/watir/rails.rb
+++ b/lib/watir/rails.rb
@@ -112,6 +112,11 @@ module Watir
             run ::Rails.application
           end
         end.to_app
+
+        # Somehow this fixes everything?
+        @app.object_id
+
+        @app
       end
 
       private

I am using rails (6.1.3.1), watir (7.0.0.beta2), watir-rspec (3.0.0), and watir-rails (2.2.2). My rails server is not starting with my test. Here's my watir specific configuration that I require in rails_helper:

require 'watir'
require 'watir/rspec'
require 'webdrivers'

Webdrivers::Chromedriver.required_version = Settings.functional_tests.webdrivers.chrome_version
Webdrivers::Geckodriver.required_version  = Settings.functional_tests.webdrivers.gecko_version
Webdrivers::Edgedriver.required_version   = Settings.functional_tests.webdrivers.edge_version

RSpec.configure do |config|
  config.add_formatter(Watir::RSpec::HtmlFormatter)

  [:acceptance, :functional].each do |type|
    config.include Watir::RSpec::Helper, type: type
    config.include Watir::RSpec::Matchers, type: type

    config.include Devise::Test::IntegrationHelpers, type: type

    config.before(:each, type: type) do
      Watir::Rails.host = 'http://localhost'

      @browser = Watir::Browser.new Settings.functional_tests.browser.to_sym
      @base_url = "#{Watir::Rails.host}:#{Watir::Rails.port}"
    end

    config.after(:each, type: type) do
      @browser.close if @browser
    end
  end
end

In my test @base_url is set and the url and the proper driver is initialized so this file is being executed.

After I started using Warden to perform sign in operations, I've faced a problem that since request is stubbed, browser cookies are no valid (i.e. if I want to grab signed in user cookies and use them in external request like curl, it won't work).

So, I think one of the approaches is to be able to get session/cookies from Rack request using already implemented middleware and use them as browser cookies (or set browser cookies to them).

I'm working on draft solution, however, not sure what approach is the best here. @jarmo What do you think would be the best way to workaround this problem?

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

So for some reason, on my machine on MacOS Mojave 10.14.6 (18G5033) line lib/watir/rails.rb:110 throws a timeout error when ran for the first time.

It seems that when checking if a server is actually running, the port number is discarded on the initial call.

Doing Net::HTTP.start('127.0.0.1', nil) { block } without a port number, picks port number 80 by default. But for some weird reason OSX already has something running on this port and then the whole call hangs with a timeout error.

Hello, I have problem when I try to update watir-rails from version 0.1.2 to 1.1.0. This problem is the same for the version 1.0.0.

When I update my gemfile

group :test do
  [...]
  gem 'watir', '~> 5.0'
  gem 'watir-rails', '1.1.0'
  gem 'watir-rspec'
  gem 'watir-webdriver'
  [...]
end

bundle command gives:

[...]
Using watir-webdriver 0.9.1
Using watir 5.0.0
Using watir-rails 1.1.0
Using watir-rspec 2.0.3
[...]

But when I run my tests, the url in the browser is wrong because it misses the rails host and the rails port. To understand why, I debugged and saw that when the test runs the goto "/app" line the method Watir::Browser::goto of watir-rails gem is not called. In fact, the method Watir::Browser::goto of watir-webdriver is called:

From: /home/darlot/.rvm/gems/ruby-2.2.2/gems/watir-webdriver-0.9.1/lib/watir-webdriver/browser.rb @ line 75 Watir::Browser#goto:

    74: def goto(uri)
 => 75:   uri = "http://#{uri}" unless uri =~ URI.regexp
    76: 
    77:   @driver.navigate.to uri
    78:   @after_hooks.run
    79: 
    80:   uri
    81: end

[1] pry(#<Watir::Browser>):1> 

So I guess I have a gem loading order problem. So I tried to change the order of the gem in the gemfile:

group :test do
 [...]
  gem 'watir-webdriver'
  gem 'watir', '~> 5.0'
  gem 'watir-rails', '1.1.0'
  gem 'watir-rspec'
 [...]
end

But this time, I obtained a infinite recursion when I run my test. Here is the console log:

# /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:53:in `initialize_rails_with_watir'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:10:in `initialize'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-5.0.0/lib/watir/loader.rb:9:in `initialize'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:53:in `block in initialize_rails_with_watir'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:36:in `call'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:36:in `override_and_preserve_original_methods'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:53:in `initialize_rails_with_watir'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:10:in `initialize'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-5.0.0/lib/watir/loader.rb:9:in `initialize'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:53:in `block in initialize_rails_with_watir'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:36:in `call'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:36:in `override_and_preserve_original_methods'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:53:in `initialize_rails_with_watir'
     # /home/sdarlot/.rvm/gems/ruby-2.2.2/gems/watir-rails-1.1.0/lib/watir/browser.rb:10:in `initialize'
     # ./spec/spec_helper.rb:85:in `new'
     # ./spec/spec_helper.rb:85:in `create_browser'
     # ./spec/spec_helper.rb:177:in `block (2 levels) in <top (required)>'

Do you have a clue to help me solving the watir-rails update ?
Thanks

I'm getting warning Browser#add_checker is deprecated. Use Browser#after_hooks#add instead.
https://github.com/watir/watir-webdriver/blob/f5e67b4335d69cd886628dd9c643d2bc5cb56084/lib/watir-webdriver/browser.rb#L289

watir-rails will not re-raise exceptions thrown by Rails Rack::App when using Rails 4.x.

Code responsible for this behavior is in Watir::Rails::Middleware#call.

Exceptions won't be even raised when Rails has action_dispatch.show_exceptions set to false and Watir::Rails.ignore_exceptions? is false.

The problem seems to be in Rails and/or Rack because enabling Thin or WEBrick logging will make everything work.

The following monkey-patch is a temporary solution until newer version of gem has been released.

Add it into your spec_helper.rb or similar file:

require "watir/rails"

class Watir::Rails
  def self.run_default_server(app, port)
    require 'rack/handler/thin'
    Rack::Handler::Thin.run(app, :Port => port)
  rescue LoadError
    require 'rack/handler/webrick'
    Rack::Handler::WEBrick.run(app, :Port => port)
  end
end