6

如果他们尝试创建用户或访问新用户路径，我正在尝试编写测试和应用程序代码以将已经登录的用户重定向到 root_path。

以下是我在 user_pages_spec.rb 中编写的测试：

describe "for signed in users" do
      let(:user) { FactoryGirl.create(:user) }
      before { sign_in user }

      describe "using a 'new' action" do
        before { get new_user_path }
        specify { response.should redirect_to(root_path) }
      end

      describe "using a 'create' action" do
        before { post users_path }
        specify { response.should redirect_to(root_path) }
      end         
  end

用户控制器：

class UsersController < ApplicationController
  before_action :unsigned_in_user, only: [:create, :new]

  def new
    @user = User.new
  end

  def create
     @user = User.new(user_params)
     if @user.save
      sign_in @user
          flash[:success] = "Welcome to the Sample App!"
          redirect_to @user
     else
          render 'new'
     end
  end

  private
    # Before filters

    def user_params
      params.require(:user).permit(:name, :email, :password,
                               :password_confirmation)
    end

    def unsigned_in_user
      puts signed_in?
      redirect_to root_url, notice: "You are already signed in." unless !signed_in?
    end
end

puts signed_in?返回错误。我假设这是问题所在，因为我希望它返回 true。以下是使用 rspec 运行测试后的错误。任何帮助表示赞赏。

Failures:

  1) User pages for signed in users using a 'create' action 
     Failure/Error: before { post users_path }
     ActionController::ParameterMissing:
       param not found: user
     # ./app/controllers/users_controller.rb:52:in `user_params'
     # ./app/controllers/users_controller.rb:20:in `create'
     # ./spec/requests/user_pages_spec.rb:162:in `block (4 levels) in <top (required)>'

  2) User pages for signed in users using a 'new' action 
     Failure/Error: specify { response.should redirect_to(root_path) }
       Expected response to be a <redirect>, but was <200>
     # ./spec/requests/user_pages_spec.rb:158:in `block (4 levels) in <top (required)>'

在 session_helper.rb 文件中：

def signed_in?
    !current_user.nil?
end

在 spec/support/utilities.rb 中：

def sign_in(user, options={})
  if options[:no_capybara]
    # Sign in when not using Capybara.
    remember_token = User.new_remember_token
    cookies[:remember_token] = remember_token
    user.update_attribute(:remember_token, User.encrypt(remember_token))
  else
    visit signin_path
    fill_in "Email",    with: user.email
    fill_in "Password", with: user.password
    click_button "Sign in"
  end
end
4

2 回答 2

4

你能让你的测试通过吗？

如果你不是，我今天遇到了和你一样的问题，并且能够通过对测试进行两项更改来通过测试 -user在 POST 时传递哈希，并使用方法no_capybara上的选项sign_in，因为get和post是不是 capybara 方法，我认为如果我们在同一个测试中从 capybara 切换到非 capybara 方法，RSpec 的行为不会像我们预期的那样。

describe "for signed-in users" do
  let(:user) { FactoryGirl.create(:user) }
  before { sign_in user, no_capybara: true }

  describe "using a 'new' action" do
    before { get new_user_path }      
    specify { response.should redirect_to(root_path) }
  end

  describe "using a 'create' action" do
    before do
      @user_new = {name: "Example User", 
                   email: "user@example.com", 
                   password: "foobar", 
                   password_confirmation: "foobar"} 
      post users_path, user: @user_new 
    end

    specify { response.should redirect_to(root_path) }
  end
end
于 2013-08-07T07:00:27.993 回答
3

答案与 najwa 相同，但我使用 FactoryGirl用户和 Rails属性方法来避免重复：

describe "using a 'create' action" do
  before { post users_path, user: user.attributes }

  specify { response.should redirect_to(root_path) }
end

有助于保持数据与测试代码的分离。

于 2013-09-07T22:41:11.290 回答