我已经在我的Rails应用程序上设置了身份验证和注册设置。当用户根据各种场景登录时,我正在使用after_sign_in_path_for()
来自定义重定向。
我问的是如何测试这种方法?它很难被隔离,因为当用户进入时,Devise会自动调用它。我想做这样的事情:
describe ApplicationController do
describe "after_sign_in_path_for" do
before :each do
@user = Factory :user
@listing = Factory :listing
sign_in @user
end
describe "with listing_id on the session" do
before :each do
session[:listing_id] = @listing.id
end
describe "and a user in one team" do
it "should save the listing from the session" do
expect {
ApplicationController.new.after_sign_in_path_for(@user)
}.to change(ListingStore, :count).by(1)
end
it "should return the path to the users team page" do
ApplicationController.new.after_sign_in_path_for(@user).should eq team_path(@user.team)
end
end
end
end
end
但这显然不是这样做的原因,因为我只是得到一个错误:
Failure/Error: ApplicationController.new.after_sign_in_path_for(@user)
RuntimeError:
ActionController::Metal#session delegated to @_request.session, but @_request is nil: #<ApplicationController:0x00000104581c68 @_routes=nil, @_action_has_layout=true, @_view_context_class=nil, @_headers={"Content-Type"=>"text/html"}, @_status=200, @_request=nil, @_response=nil>
那么,我该如何测试这种方法呢?
答案 0 :(得分:32)
describe ApplicationController do
controller do
def after_sign_in_path_for(resource)
super resource
end
end
before (:each) do
@user = FactoryGirl.create(:user)
end
describe "After sigin-in" do
it "redirects to the /jobs page" do
controller.after_sign_in_path_for(@user).should == jobs_path
end
end
end
答案 1 :(得分:4)
在类似的说明中 - 如果您想在注册后测试重定向,则有两种选择。
首先,您可以遵循与上述类似的模式,并直接在RegistrationsController中测试该方法:
require 'spec_helper'
describe RegistrationsController do
controller(RegistrationsController) do
def after_sign_up_path_for(resource)
super resource
end
end
describe "After sign-up" do
it "redirects to the /organizations/new page" do
@user = FactoryGirl.build(:user)
controller.after_sign_up_path_for(@user).should == new_organization_path
end
end
end
或者,您可以采用更加集成测试的方法,并执行以下操作:
require 'spec_helper'
describe RegistrationsController do
describe "After successfully completing the sign-up form" do
before do
@request.env["devise.mapping"] = Devise.mappings[:user]
end
it "redirects to the new organization page" do
post :create, :user => {"name" => "Test User", "email" => "test@example.com", "password" => "please"}
response.should redirect_to(new_organization_path)
end
end
end
答案 2 :(得分:1)
我最近通过Google找到了这个答案,并认为我会添加我的解决方案。我不喜欢被接受的答案,因为它正在测试应用程序控制器上方法的返回值,而不是测试应用程序的预期行为。
我最终只是测试了呼叫以创建一个新会话作为请求规范。
POST
(路轨5,设计4,RSpec 3)
答案 3 :(得分:0)
context "without previous page" do
before do
Factory.create(:user, email: "junior@example.com", password: "123456", password_confirmation: "123456")
request.env["devise.mapping"] = Devise.mappings[:user]
post :create, user: { email: "junior@example.com", password: "123456" }
end
end
it { response.should redirect_to(root_path) }
context "with previous page" do
before do
Factory.create(:user, email: "junior@example.com", password: "123456", password_confirmation: "123456")
request.env["devise.mapping"] = Devise.mappings[:user]
request.env['HTTP_REFERER'] = 'http://test.com/restaurants'
post :create, user: { email: "junior@example.com", password: "123456" }
end
it { response.should redirect_to("http://test.com/restaurants") }
end
答案 4 :(得分:0)
对于新来者,我建议这样做:
RSpec.describe ApplicationController, type: :controller do
let(:user) { create :user }
describe "After sing-in" do
it "redirects to the /yourpath/ home page" do
expect(subject.after_sign_in_path_for(user)).to eq(yourpath_root_path)
end
end
end