Question

绝对最好划分规格，以便你有关于MVC架构各个方面的规范，但我认为与控制器规格和视图规格有轻微的交叉。

使用视图规范，你应该只关注视图，但是对于控制器规范，我仍然认为测试正确的视图是否是一个好主意，甚至可能测试视图的内容，尽管更多内容的深入测试应该在视图规范中进行。

尽管有一篇明确的文章https://www.relishapp.com/rspec/rspec-rails/v/2-1/docs/controller-specs/render-views，描述了如何做到这一点，但我无法集成我的视图和控制器规范。

我一直收到错误未定义的方法'包含'！

这是我的spec_helper：

# This file is copied to spec/ when you run 'rails generate rspec:install'
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'


require 'capybara/rspec'
require 'capybara/rails'

require 'factory_girl_rails'
require 'ap'

def set(factory)
  @user = FactoryGirl.create(factory) 
end

def sign_up(first_name, last_name, profile_name, email, password)
    visit "/"
    click_link "Register"
    fill_in('First name', with: first_name)
    fill_in('Last name', with: last_name)            
    fill_in('Profile name', with: profile_name)
    fill_in('Email', with: email)
    fill_in('Password', with: password)
    fill_in('Password confirmation', with: password)
    click_button 'Sign up'
end

def sign_in(email, password)
    visit "/"
    click_link "Sign In"
    fill_in('Email', with: email)
    fill_in('Password', with: password)
    click_button 'Sign in'
end

def sign_out
    visit "/"
    click_link "Sign Out"
end



#Webrat.configure do |config|
#  config.mode = :rails
#end

#webrat

require 'capybara/poltergeist'
# Capybara.javascript_driver = :poltergeist


Capybara.javascript_driver = :selenium


Dir[Rails.root.join("spec/support/**/*.rb")].each { |f| require f }

# Checks for pending migrations before tests are run.
# If you are not using ActiveRecord, you can remove this line.
ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration)


RSpec.configure do |config|
  # true means 'yes, filter these specs'
  config.filter_run_excluding stress: true
 # config.current_driver = :webkit
#  config.use_transactional_fixtures = false

#  config.include Capybara::DSL


  DatabaseCleaner.strategy = :truncation


  config.after(:suite) do
    DatabaseCleaner.clean_with(:truncation)
  end

#  config.before(:suite) do
  #  DatabaseCleaner.strategy = :transaction
 #   DatabaseCleaner.clean_with(:truncation)
#    DatabaseCleaner.start
 # end

 # config.after(:each) do
 #   DatabaseCleaner.clean
 # end

  #config.after(:suite) do
#   DatabaseCleaner.strategy = :transaction
#   DatabaseCleaner.clean_with(:truncation)
  #  DatabaseCleaner.clean
 # end


  # Remove this line if you're not using ActiveRecord or ActiveRecord fixtures
  # config.fixture_path = "#{::Rails.root}/spec/fixtures"

  # config.include RSpec::Rails::RequestExampleGroup, type: :feature

  # If you're not using ActiveRecord, or you'd prefer not to run each of your
  # examples within a transaction, remove the following line or assign false
  # instead of true.
  config.use_transactional_fixtures = true



  I18n.enforce_available_locales = true

  # If true, the base class of anonymous controllers will be inferred
  # automatically. This will be the default behavior in future versions of
  # rspec-rails.
  config.infer_base_class_for_anonymous_controllers = false

  # 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"
end

这是我的控制器规范：

require "spec_helper"

describe UserFriendshipsController, type: :controller do
    render_views
    let (:user_1) { FactoryGirl.create(:user_1)} 

    before { 
        sign_in user_1
        get :index
    }   

    it "renders the :index view" do
        response.should render_template(:index)
    end

    it "view contains expected html" do
        # a sanity test more than anything
        response.should contain("Welcome to the home page")
    end
end

运行此规范后，我得到了这个：

.F

Failures:

  1) UserFriendshipsController view contains expected html
     Failure/Error: response.should contain("Listing widgets")
     NoMethodError:
       undefined method `contain' for #<RSpec::Core::ExampleGroup::Nested_1:0x00000008632268>
     # ./spec/controllers/user_friendships_spec.rb:18:in `block (2 levels) in <top (required)>'

Finished in 0.1835 seconds
2 examples, 1 failure

为什么会这样？我怎样才能让它发挥作用？

Answer 1

如果您查看relish documentation for the current 2.14 version of Rspec，您会看到他们现在正在使用match：

expect(response.body).to match /Listing widgets/m

使用should语法，这应该有效：

response.body.should match(/Welcome to the home page/)

Answer 2

是的，来自Rspec的一篇非常不清楚的文章引起了这个错误。它在其示例中使用了webrat，并没有想到要告诉你。如果有其他人到这里，您可以将webrat添加到gemfile中以使用contains方法：

的Gemfile

group :test do
    gem 'webrat'
end

然而，使用rspec的本机匹配方法更有意义：

expect(response.body).to match /Listing widgets/m

控制器规范的未定义方法“包含”

2 个答案: