ruby 我如何在RSpec测试中访问巫术？

8ftvxx2r  于 2023-04-11  发布在  Ruby
关注(0)|答案(5)|浏览(127)

巫术鉴定宝石：https://github.com/NoamB/sorcery
Sorcery的创建者提供了一个示例Rails应用程序，其Test：：Unit功能测试中包含Sorcery测试帮助程序：https://github.com/NoamB/sorcery-example-app/blob/master/test/functional/users_controller_test.rb

# Test::Unit functional test example
require 'test_helper'

class UsersControllerTest < ActionController::TestCase
  setup do
    @user = users(:noam)
  end

  test "should show user" do
    login_user
    get :show, :id => @user.to_param
    assert_response :success
  end

但是我不知道如何让login_user在我的RSpec控制器规范中工作。

/gems/sorcery-0.7.5/lib/sorcery/test_helpers/rails.rb:7:in `login_user': 
undefined method `auto_login' for nil:NilClass (NoMethodError)

以下是Sorcery gem中关于上述错误的相关代码：https://github.com/NoamB/sorcery/blob/master/lib/sorcery/test_helpers/rails.rb

module Sorcery
  module TestHelpers
    module Rails
      # logins a user and calls all callbacks
      def login_user(user = nil)
        user ||= @user
        @controller.send(:auto_login,user)
        @controller.send(:after_login!,user,[user.send(user.sorcery_config.username_attribute_names.first),'secret'])
      end

      def logout_user
        @controller.send(:logout)
      end
    end
  end
end

更新：

根据Sorcery的文档“Testing in Rails 3”，我确实将include Sorcery::TestHelpers::Rails添加到了我的spec_helper.rb中。
巫术测试助手login_user作用于@controller，但我得到了错误，因为在我的控制器规范中@controller是nil。下面是我的规范：

#spec/controllers/forums_controller_spec.rb
require 'spec_helper'

describe ForumsController do
  render_views

  describe 'GET new' do
    describe 'when guest' do
      it 'should deny and redirect' do
        get :new
        response.should redirect_to(root_path)
      end
    end

    describe 'when admin' do
      p @controller #=> nil
      @user = User.create!(username: "Test", password: "secret", email: "test@test.com")
      login_user # <--------------- where the error occurs
      it 'should resolve' do
        get :new
        response.should render_template(:new)
      end
    end
  end
end
ruby

5条答案

按热度按时间
aij0ehis

aij0ehis1#

FWIW，我花了很多时间寻找这个问题的答案。我正在使用水豚和rSpec。事实证明，你需要手动登录到使用巫术才能让登录工作。
我在这里创建了一个关于使用Sorcery/Rspec/Capybara创建集成测试的Gist：https://gist.github.com/2359120/9989c14af19a48ba726240d030c414b882b96a8a

赞(0）分享  回复(0）举报  2023-04-11
iqxoj9l9

iqxoj9l92#

您需要在spec_helper中包含Sorcery测试助手

include Sorcery::TestHelpers::Rails

参见魔法wiki：https://github.com/NoamB/sorcery/wiki/Testing-rails-3
在示例rails应用程序中，这是在www.example.com上完成https://github.com/NoamB/sorcery-example-app/blob/master/test/test_helper.rb#L13

更新

你在同一个文件夹中是否有其他的控制器规格成功通过？RSpec通常会在“spec/controllers”文件夹中混合控制器测试所需的东西。
您可以尝试通过编写以下代码将其显式标记为控制器规范

describe ForumsController, :type => :controller do
赞(0）分享  回复(0）举报  2023-04-11
h9a6wy2h

h9a6wy2h3#

你需要把你的用户创建和登录放在before（：each）块中，如下所示：

describe 'when admin' do
  before(:each) do
    @user = User.create!(username: "Test", password: "secret", email: "test@test.com")
    login_user
  end

  it 'should resolve' do
    get :new
    response.should render_template(:new)
  end
end
赞(0）分享  回复(0）举报  2023-04-11
68bkxrlz

68bkxrlz4#

对于Rails 7.0.0中的新应用程序，我通过添加以下内容修复了此问题：

# spec/rails_helper.rb

config.include ::Sorcery::TestHelpers::Rails::Controller

然后我可以使用魔法中的方法，而不需要定义我自己的方法：

# spec/controllers/registrations_controller_spec.rb
require 'rails_helper'

RSpec.describe RegistrationsController, type: :controller do
   let(:current_user) { nil }

   before do
      login_user(current_user) if current_user
   end

   describe "when user is logged in" do
      let(:current_user) { create(:user) }
      it "action new redirects to root" do
         get :new

         expect(subject).to redirect_to(root_path)
         expect(flash[:notice]).to eq(I18n.t("registration.new.already_logged_in"))
      end
   end
end

只添加：：Sorcery：：TestHelpers：：Rails无法找到login_user方法。
希望这能帮上忙。

赞(0）分享  回复(0）举报  2023-04-11
jpfvwuh4

jpfvwuh45#

我自己刚刚经历了这个困境，并从danneu，diwalak和Birdlevitator的输入中汲取了经验（在此标题中：rail3/rspec/devise: rspec controller test fails unless I add a dummy=subject.current_user.inspect）我想我能看到一个解决方案。
我一直在使用一个标准的rails 3 rspec生成的资源，它是通过'rails generate scaffold'命令生成的。下面是我修改后的控制器rspec文件，它可以使用魔法登录：

require 'spec_helper'

# This spec was generated by rspec-rails when you ran the scaffold generator.
# It demonstrates how one might use RSpec to specify the controller code that
# was generated by Rails when you ran the scaffold generator.
#
# It assumes that the implementation code is generated by the rails scaffold
# generator.  If you are using any extension libraries to generate different
# controller code, this generated spec may or may not pass.
#
# It only uses APIs available in rails and/or rspec-rails.  There are a number
# of tools you can use to make these specs even more expressive, but we're
# sticking to rails and rspec-rails APIs to keep things simple and stable.
#
# Compared to earlier versions of this generator, there is very limited use of
# stubs and message expectations in this spec.  Stubs are only used when there
# is no simpler way to get a handle on the object needed for the example.
# Message expectations are only used when there is no simpler way to specify
# that an instance is receiving a specific message.

describe RecordsController do

  before(:each) do
    @user = User.create!(forename: "Billy", surname: "Bob", username: "Test", password: "secret!1", email: "test@test.com")
    login_user
  end

  # This should return the minimal set of attributes required to create a valid
  # Record. As you add validations to Record, be sure to
  # update the return value of this method accordingly.
  def valid_attributes
    { :owner => 'Mr Blobby', :catagory => 'Index'}
  end

  # This should return the minimal set of values that should be in the session
  # in order to pass any filters (e.g. authentication) defined in
  # RecordsController. Be sure to keep this updated too.
  def valid_session
    {"warden.user.user.key" => session["warden.user.user.key"]}
  end

  describe "GET index" do
    it "assigns all records as @records" do
      record = Record.create! valid_attributes
      get :index, {}, valid_session
      assigns(:records).should eq([record])
    end
  end

  describe "GET show" do
    it "assigns the requested record as @record" do
      record = Record.create! valid_attributes
      get :show, {:id => record.to_param}, valid_session
      assigns(:record).should eq(record)
    end
  end

  describe "GET new" do
    it "assigns a new record as @record" do
      get :new, {}, valid_session
      assigns(:record).should be_a_new(Record)
    end
  end

  describe "GET edit" do
    it "assigns the requested record as @record" do
      record = Record.create! valid_attributes
      get :edit, {:id => record.to_param}, valid_session
      assigns(:record).should eq(record)
    end
  end

  describe "POST create" do
    describe "with valid params" do
      it "creates a new Record" do
        expect {
          post :create, {:record => valid_attributes}, valid_session
        }.to change(Record, :count).by(1)
      end

      it "assigns a newly created record as @record" do
        post :create, {:record => valid_attributes}, valid_session
        assigns(:record).should be_a(Record)
        assigns(:record).should be_persisted
      end

      it "redirects to the created record" do
        post :create, {:record => valid_attributes}, valid_session
        response.should redirect_to(Record.last)
      end
    end

    describe "with invalid params" do
      it "assigns a newly created but unsaved record as @record" do
        # Trigger the behavior that occurs when invalid params are submitted
        Record.any_instance.stub(:save).and_return(false)
        post :create, {:record => {}}, valid_session
        assigns(:record).should be_a_new(Record)
      end

      it "re-renders the 'new' template" do
        # Trigger the behavior that occurs when invalid params are submitted
        Record.any_instance.stub(:save).and_return(false)
        post :create, {:record => {}}, valid_session
        response.should render_template("new")
      end
    end
  end

  describe "PUT update" do
    describe "with valid params" do
      it "updates the requested record" do
        record = Record.create! valid_attributes
        # Assuming there are no other records in the database, this
        # specifies that the Record created on the previous line
        # receives the :update_attributes message with whatever params are
        # submitted in the request.
        Record.any_instance.should_receive(:update_attributes).with({'these' => 'params'})
        put :update, {:id => record.to_param, :record => {'these' => 'params'}}, valid_session
      end

      it "assigns the requested record as @record" do
        record = Record.create! valid_attributes
        put :update, {:id => record.to_param, :record => valid_attributes}, valid_session
        assigns(:record).should eq(record)
      end

      it "redirects to the record" do
        record = Record.create! valid_attributes
        put :update, {:id => record.to_param, :record => valid_attributes}, valid_session
        response.should redirect_to(record)
      end
    end

    describe "with invalid params" do
      it "assigns the record as @record" do
        record = Record.create! valid_attributes
        # Trigger the behavior that occurs when invalid params are submitted
        Record.any_instance.stub(:save).and_return(false)
        put :update, {:id => record.to_param, :record => {}}, valid_session
        assigns(:record).should eq(record)
      end

      it "re-renders the 'edit' template" do
        record = Record.create! valid_attributes
        # Trigger the behavior that occurs when invalid params are submitted
        Record.any_instance.stub(:save).and_return(false)
        put :update, {:id => record.to_param, :record => {}}, valid_session
        response.should render_template("edit")
      end
    end
  end

  describe "DELETE destroy" do
    it "destroys the requested record" do
      record = Record.create! valid_attributes
      expect {
        delete :destroy, {:id => record.to_param}, valid_session
      }.to change(Record, :count).by(-1)
    end

    it "redirects to the records list" do
      record = Record.create! valid_attributes
      delete :destroy, {:id => record.to_param}, valid_session
      response.should redirect_to(records_url)
    end
  end

end

下面是一些重要的部分：
这一步完成了编程式登录（忽略名字和姓氏属性，它们是我正在构建的解决方案所特有的）：

before(:each) do
    @user = User.create!(forename: "Billy", surname: "Bob", username: "Test", password: "secret!1", email: "test@test.com")
    login_user
end

此位保存会话信息/密钥数据：

def valid_session
    {"warden.user.user.key" => session["warden.user.user.key"]}
end

正如diwalak所写的，我们需要将以下内容添加到spec_help.rb文件中：

include Sorcery::TestHelpers::Rails

就这样--反正对我很有效：）

赞(0）分享  回复(0）举报  2023-04-11
我来回答

相关问题

    查看更多

    热门标签

    更多
    JavaquerypythonNode开发语言requestUtil数据库Table后端算法LoggerMessageElementParser

    最新问答

    更多
    • 蜀ICP备2022004421号-2 NULL123 https://www.null123.com © All rights reserved
    • 本站内容来源互联网,如果侵犯您的权益请联系我们删除, 联系方式：448109455@qq.com