Rspec-rails - expected helper_method behaviour in view specs

okkezSS · November 10, 2010, 5:01pm

Heya,

Say I had the following app controller :
class ApplicationController<ActionController::Base
def logged_in?
true
end
helper_method :logged_in?
end

Under a rspec-rails1 view-spec, a view template would be able to call
logged_in?. It seems this behaviour has gone away in rspec-rails2.
Was this behaviour intentional? What’s the recommended alternative -
mixing in a helper to stub out all these methods with
config.include(HelperMethodsStubber, :type=>:view) ?

In addition, rspec-rails1 used to mix all helpers into the view
template, right? rspec-rails2 mixes in only the ApplicationHelper
and the helper for the current spec, but this seems a strange choice
when Rails includes all helpers by default.

Any thoughts?

-Jonathan

Jonathan_del_Stroth · November 11, 2010, 9:39am

Not sure why helper_method doesn’t work, but just helper definetely
works for us

github.com

rails/rails/blob/main/actionpack/lib/abstract_controller/helpers.rb#L96


      
            klass._helpers = nil
          
          
  klass.class_eval { default_helper_module! } unless klass.anonymous?
            super
          end
          
          
attr_writer :_helpers
          
          
include Resolution
          
          
##
          # :method: modules_for_helpers
          # :call-seq: modules_for_helpers(modules_or_helper_prefixes)
          #
          # Given an array of values like the ones accepted by +helper+, this method
          # returns an array with the corresponding modules, in the same order.
          #
          #--
          # Implemented by Resolution#modules_for_helpers.
          
          
##

(supports various ways to specify desired helper).

+1 on question about Rails including all helpers vs. RSpec doing it
the Rails 2 way

On Wed, Nov 10, 2010 at 3:18 AM, Jonathan del Strother