ruby on rails-使用rspec进行测试.consider_all_requests_local=false



我在应用程序控制器中使用:类似的.consider_all_requests_local

  unless Rails.application.config.consider_all_requests_local
    rescue_from ActionController::InvalidCrossOriginRequest, :with => :render_404
  end

如果引发ActionController::InvalidCrossOriginRequest,则返回404。在本地环境中,它不会被提升,有利于调试。对于这部分来说,它是有效的。但我想用rspec测试一下。

我试过类似的东西

describe 'ActionController::InvalidCrossOriginRequest render 404' do
    before { Rails.application.config.consider_all_requests_local = false }
    controller do
      def index
        raise ActionController::InvalidCrossOriginRequest
      end
    end
    subject { xhr :get, :index, format: :js }
    its(:status) { is_expected.to eq 404 }
end

有两件事。我可能没有以正确的方式抚养孩子。在本地,调用mywebsite.com/editor/fckeditor.js时会发生错误。找不到调用特定url的方法。

第二个问题,之前的不会更改Rails.application.config.consider_all_requests_local状态。

我得到:

1) ApplicationController ActionController::InvalidCrossOriginRequest render 404 status
     Failure/Error: raise ActionController::InvalidCrossOriginRequest
     ActionController::InvalidCrossOriginRequest:
       ActionController::InvalidCrossOriginRequest

该问题似乎是由在类加载时执行的unless检查引起的。这意味着第一次加载类时,将检查应用程序配置中的值,并且设置或不设置rescue_from

最基本的解决方法是,一旦更改了设置,就需要使用load来重新读取该文件。然而,按原样,一旦rescue_from打开,再次加载文件不会导致它关闭

下一种选择是使用rescue_from(with:),它将委托给一个辅助对象或块形式。您可以使用此辅助对象来检查值并处理条件或不处理条件。然而,考虑到这看起来只是你只想在非生产环境中做的事情,你可以将两者结合起来。使用unless验证您是否未在生产中,然后每次使用with检查配置。

类似于:

class ApplicationController < ActionController::Base
  unless Rails.env.production?
    rescue_from ActionController::InvalidCrossOriginRequest do
      unless Rails.application.config.consider_all_requests_local
        render_404
      end
    end
  end
end

试着嘲笑它而不是设置:

before { Rails.stub_chain('application.config.consider_all_requests_local').and_return(false) }

更多信息点击这里

此语法已弃用,因此您可以关闭弃用警告或使用新的"变通方法"

allow(object).to receive_message_chain(:one, :two, :three).and_return(:four)
expect(object.one.two.three).to eq(:four)

如张贴在这里

我过去也有一个警卫在我的rescue_from配置周围,比如:

unless Rails.application.config.consider_all_requests_local
  rescue_from Exception, with: :render_error
  …
end

它运行得很好,直到我试图弄清楚如何让它处理错误,并在一些测试中显示非常自定义的错误页面(就像在生产中一样)@Aaron K的回答有助于解释为什么不能在类定义中评估检查,而必须在实际的错误处理程序中(在运行时)进行检查。但这只解决了我的部分问题

以下是我所做的。。。

ApplicationController中,如果show_detailed_exceptions标志(比consider_all_requests_local更合适的检查)为真,请记住重新引发任何错误。换句话说,只有当应用程序/请求配置为处理生产错误时,才进行生产错误处理;否则"通过"并重新引发错误。

  rescue_from Exception,                           with: :render_error
  rescue_from ActiveRecord::RecordNotFound,        with: :render_not_found
  rescue_from ActionController::RoutingError,      with: :render_not_found
  rescue_from AbstractController::ActionNotFound,  with: :render_not_found
  def show_detailed_exceptions?
    # Rails.application.config.consider_all_requests_local causes this to be set to true as well.
    request.get_header("action_dispatch.show_detailed_exceptions")
  end
  def render_not_found(exception = nil, template = 'errors/not_found')
    raise exception if show_detailed_exceptions?
    logger.error exception if exception
    render template, formats: [:html], status: :not_found
  end
  def render_error(exception)
    raise exception if show_detailed_exceptions?
    deliver_exception_notification(exception)
    logger.error exception
    # Prevent AbstractController::DoubleRenderError in case we've already rendered something
    method(:response_body=).super_method.call(nil)
    respond_to do |format|
      format.html { render 'errors/internal_server_error', formats: [:html], status: :internal_server_error }
      format.any  { raise exception }
    end
  end

添加到spec/support/handle_exceptions_like_production.rb:

shared_context 'handle_exceptions_like_production', handle_exceptions_like_production: true do
  before do |example|
    case example.metadata[:type]
    when :feature
      method = Rails.application.method(:env_config)
      allow(Rails.application).to receive(:env_config).with(no_args) do
        method.call.merge(
          'action_dispatch.show_exceptions' => true,
          'action_dispatch.show_detailed_exceptions' => false,
          'consider_all_requests_local' => true
        )
      end
    when :controller
      # In controller tests, we can only test *controller* behavior, not middleware behavior.  We
      # can disable show_detailed_exceptions here but we can *only* test any behaviors that depend
      # on it that are defined in our *controller* (ApplicationController). Because the request
      # doesn't go through the middleware (DebugExceptions, ShowExceptions) — which is what actually
      # renders the production error pages — in controller tests, we may not see the exact same
      # behavior as we would in production. Feature (end-to-end) tests may be needed to more
      # accurately simulate a full production stack with middlewares.
      request.set_header 'action_dispatch.show_detailed_exceptions', false
    else
      raise "expected example.metadata[:type] to be one of :feature or :controller but was #{example.metadata[:type]}"
    end
  end
end
RSpec.configure do |config|
  config.include_context 'handle_exceptions_like_production', :handle_exceptions_like_production
end

然后,在端到端(功能)测试中,您希望它像在生产中那样处理异常(换句话说,为了而不是将其视为本地请求),只需将:handle_exceptions_like_production添加到您的示例组中:

describe 'something', :handle_exceptions_like_production do
  it …
end

例如:

spec/features/exception_handling_spec.rb:

describe 'exception handling', js: false do
  context 'default behavior' do
    it do |example|
      expect(example.metadata[:handle_exceptions_like_production]).to eq nil
    end
    describe 'ActiveRecord::RecordNotFound' do
      it do
        expect {
          visit '/users/0'
        }.to raise_exception(ActiveRecord::RecordNotFound)
      end
    end
    describe 'ActionController::RoutingError' do
      it do
        expect {
          visit '/advertisers/that_track_you_and_show_you_personalized_ads/'
        }.to raise_exception(ActionController::RoutingError)
      end
    end
    describe 'RuntimeError => raised' do
      it do
        expect {
          visit '/test/exception'
        }.to raise_exception(RuntimeError, 'A test exception')
      end
    end
  end
  context 'when :handle_exceptions_like_production is true', :handle_exceptions_like_production do
    describe 'ActiveRecord::RecordNotFound => production not_found page' do
      it do
        expect {
          visit '/users/0'
        }.to_not raise_exception
        expect_not_found
      end
    end
    describe 'ActionController::RoutingError => production not_found page' do
      it do
        visit '/advertisers/that_track_you_and_show_you_personalized_ads/'
        expect_not_found
      end
    end
    describe 'RuntimeError => production not_found page' do
      it do
        visit '/test/exception'
        expect_application_error
      end
    end
  end
end

它也可以用于控制器测试——如果您在ApplicationController中定义了生产错误处理。spec/controllers/exception_handling_spec.rb:

describe 'exception handling' do
  context 'default behavior' do
    describe UsersController do
      it do
        expect {
          get 'show', params: {id: 0}
        }.to raise_exception(ActiveRecord::RecordNotFound)
      end
    end
    describe TestController do
      it do
        expect {
          get 'exception'
        }.to raise_exception(RuntimeError, 'A test exception')
      end
    end
  end
  context 'when handle_exceptions_like_production: true', :handle_exceptions_like_production do
    describe UsersController do
      it do
        expect {
          get 'show', params: {id: 0}
        }.to_not raise_exception
        expect(response).to render_template('errors/not_found')
      end
    end
    describe TestController do
      it do
        expect {
          get 'exception'
        }.to_not raise_exception
        expect(response).to render_template('errors/internal_server_error')
      end
    end
  end
end

使用:rspec 3.9rails 5.2

进行测试

相关内容

  • 没有找到相关文章

最新更新