在編寫請求規範時,如何設置會話和/或存根控制器方法? 我想在我的集成測試存根出認證 - RSpec的/請求請求中的Stubbing驗證規範
這是一個測試的例子
require File.dirname(__FILE__) + '/../spec_helper'
require File.dirname(__FILE__) + '/authentication_helpers'
describe "Messages" do
include AuthenticationHelpers
describe "GET admin/messages" do
before(:each) do
@current_user = Factory :super_admin
login(@current_user)
end
it "displays received messages" do
sender = Factory :jonas
direct_message = Message.new(:sender_id => sender.id, :subject => "Message system.", :content => "content", :receiver_ids => [@current_user.id])
direct_message.save
get admin_messages_path
response.body.should include(direct_message.subject)
end
end
end
助手:
module AuthenticationHelpers
def login(user)
session[:user_id] = user.id # session is nil
#controller.stub!(:current_user).and_return(user) # controller is nil
end
end
而ApplicationController中,處理認證:
class ApplicationController < ActionController::Base
protect_from_forgery
helper_method :current_user
helper_method :logged_in?
protected
def current_user
@current_user ||= User.find(session[:user_id]) if session[:user_id]
end
def logged_in?
!current_user.nil?
end
end
爲什麼它不是possi可以訪問這些資源嗎?
1) Messages GET admin/messages displays received messages
Failure/Error: login(@current_user)
NoMethodError:
undefined method `session' for nil:NilClass
# ./spec/requests/authentication_helpers.rb:3:in `login'
# ./spec/requests/message_spec.rb:15:in `block (3 levels) in <top (required)>'
感謝大衛。它工作得很好,但它似乎有點矯枉過正,使所有這些要求? – 2011-04-27 11:52:52
如果我認爲這是過度殺傷,我不會推薦它:) – 2011-04-27 12:54:32
這也是最可靠的方法。 'ActionDispatch :: IntegrationTest'旨在模擬一個或多個用戶通過瀏覽器進行交互,而不必使用真正的瀏覽器。可能有多個用戶(即會話)以及一個示例中的多個控制器,並且會話/控制器對象是上次請求中使用的那些對象。請求前您無權訪問它們。 – 2011-04-27 13:02:45