使用Rails 4.x安裝RSpec，Capybara和Selenium Webdriver

我在使用Hartl's RoR tutorial，但更新了軟件版本。你能告訴我如何設置測試工具（運行什麼命令，以及spec_helper的全部內容應該是什麼）。當我嘗試從終端運行RSpec時，出現各種錯誤。通過要求StackOverflow建議的文件修復一個錯誤會暴露另一個錯誤。我想創建一個正確方式的wiki來設置Capybara + RSpec與Rails。使用Rails 4.x安裝RSpec，Capybara和Selenium Webdriver

的Gemfile：

source 'https://rubygems.org' 
ruby '2.1.2' 

gem 'rails', '4.1.0' 

group :development, :test do 
    gem 'sqlite3', '1.3.8' 
    gem 'rspec-rails', '>= 3.0.0' 
end 

group :test do 
    gem 'selenium-webdriver', '>=2.35.1' 
    gem 'capybara', '>=2.4.1' 
end 

gem 'sass-rails', '4.0.1' 
gem 'uglifier', '2.1.1' 
gem 'coffee-rails', '4.0.1' 
gem 'jquery-rails', '3.0.4' 
gem 'turbolinks', '1.1.1' 
gem 'jbuilder', '1.0.2' 

group :doc do 
    gem 'sdoc', '0.3.20', require: false 
end 

group :production do 
    gem 'pg', '0.15.1' 
    gem 'rails_12factor', '0.0.2' 
end

規格/ spec_helper.rb

require 'active_support' 
require 'rails/all' 

require 'rspec/rails' 
require 'rspec/autorun' 


# This file was generated by the `rails generate rspec:install` command. Conventionally, all 
# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`. 
# The generated `.rspec` file contains `--require spec_helper` which will cause this 
# file to always be loaded, without a need to explicitly require it in any files. 
# 
# Given that it is always loaded, you are encouraged to keep this file as 
# light-weight as possible. Requiring heavyweight dependencies from this file 
# will add to the boot time of your test suite on EVERY test run, even for an 
# individual file that may not need all of that loaded. Instead, make a 
# separate helper file that requires this one and then use it only in the specs 
# that actually need it. 
# 
# The `.rspec` file also contains a few flags that are not defaults but that 
# users commonly want. 
# 
# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration 
RSpec.configure do |config| 
# The settings below are suggested to provide a good initial experience 
# with RSpec, but feel free to customize to your heart's content. 
=begin 
    # These two settings work together to allow you to limit a spec run 
    # to individual examples or groups you care about by tagging them with 
    # `:focus` metadata. When nothing is tagged with `:focus`, all examples 
    # get run. 
    config.filter_run :focus 
    config.run_all_when_everything_filtered = true 

    # Many RSpec users commonly either run the entire suite or an individual 
    # file, and it's useful to allow more verbose output when running an 
    # individual spec file. 
    if config.files_to_run.one? 
    # Use the documentation formatter for detailed output, 
    # unless a formatter has already been configured 
    # (e.g. via a command-line flag). 
    config.default_formatter = 'doc' 
    end 

    # Print the 10 slowest examples and example groups at the 
    # end of the spec run, to help surface which specs are running 
    # particularly slow. 
    config.profile_examples = 10 

    # Run specs in random order to surface order dependencies. If you find an 
    # order dependency and want to debug it, you can fix the order by providing 
    # the seed, which is printed after each run. 
    #  --seed 1234 
    config.order = :random 

    # Seed global randomization in this process using the `--seed` CLI option. 
    # Setting this allows you to use `--seed` to deterministically reproduce 
    # test failures related to randomization by passing the same `--seed` value 
    # as the one that triggered the failure. 
    Kernel.srand config.seed 

    # rspec-expectations config goes here. You can use an alternate 
    # assertion/expectation library such as wrong or the stdlib/minitest 
    # assertions if you prefer. 
    config.expect_with :rspec do |expectations| 
    # Enable only the newer, non-monkey-patching expect syntax. 
    # For more details, see: 
    # - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax 
    expectations.syntax = :expect 
    end 

    # rspec-mocks config goes here. You can use an alternate test double 
    # library (such as bogus or mocha) by changing the `mock_with` option here. 
    config.mock_with :rspec do |mocks| 
    # Enable only the newer, non-monkey-patching expect syntax. 
    # For more details, see: 
    # - http://teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/ 
    mocks.syntax = :expect 

    # Prevents you from mocking or stubbing a method that does not exist on 
    # a real object. This is generally recommended. 
    mocks.verify_partial_doubles = true 
    end 
=end 
# require 'rails/all' 
# require 'capybara/rails' 
# require 'capybara/rspec' 
end

當前出錯：

$ rspec 
/home/neilsatra/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:73: warning: loading in progress, circular require considered harmful - /home/neilsatra/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/capybara-2.4.1/lib/capybara.rb 
     from /home/neilsatra/.rbenv/versions/2.1.2/bin/rspec:23:in `<main>' 
     from /home/neilsatra/.rbenv/versions/2.1.2/bin/rspec:23:in `load'

以前的錯誤（這樣的人可以谷歌這個答案）：

個

的形式是「未初始化的常數（NameError）」，其中一些可能是「的ActiveSupport ::自動加載」，「導軌」或「::的ActionView ::模板處理程序:: ERB :: ENCODING_FLAG」

的各種錯誤相關我已經看了看問題的：把一切都在一個組

來源

2014-07-25 Neil

它似乎與您的水豚錯誤沒有關係，但您不需要在spec_helper.rb中'require'activesupport''或'require'rails/all''。 –

，我不能讓它與你的答案@ auL5agoi甚至工作，而不得不求助於具有確切重新啓動項目本教程中規定的寶石版本，之後它的工作完美無瑕。

來源

2014-08-03 22:44:26 Neil

嘗試，我認爲這是值得一試。像：

group :development, :test do 
    gem 'rspec-rails', '>= 3.0.0' 
    gem 'selenium-webdriver', '>=2.35.1' 
    gem 'capybara', '>=2.4.1' 
end

幫我出：

我把我的spec_helper.rb

config.include Capybara::DSL

這這可能是矯枉過正，但我也做的是：

spec_helper.rb：

require "capybara"

我在運行當前目錄下的測試時也遇到了奇怪的行爲。爲了解決這個問題只需移動1個目錄並像這樣運行：最終

bundle exec rspec specs/features/examples_spec.rb

來源

2014-07-25 14:46:34

使用Rails 4.x安裝RSpec，Capybara和Selenium Webdriver

回答

相關問題