Skip to main content

Testing view helpers



I'm currently working on a Rails plugin used for generating iPhone specific HTML meta-tags. I'm trying to use ActionView::TestCase for unit tests but keep getting the same error. See file contents and error below. Any ideas or help would be much appreciated.





test_helper.rb







require 'rubygems'

require 'test/unit'

require 'active_support'

require 'action_view'

require File.join(File.dirname(__FILE__), '..', 'lib', 'iphone_helper')







iphone_test_helper.rb







require 'test_helper'



class IphoneHelperTest < ActionView::TestCase

test 'br' do

tag = tag('br')

assert_tag_in tag, '<br />'

end

end







error







RuntimeError: In order to use #url_for, you must include routing helpers explicitly. For instance, `include Rails.application.routes.url_helpers




Comments

  1. Awful and hacky workaround that worked for me (since I am working on a gem and not in a full rails environment):

    require 'ostruct'

    module ActionController::UrlFor
    def _routes
    helpers = OpenStruct.new
    helpers.url_helpers = Module.new
    helpers
    end
    end

    ReplyDelete
  2. Did you try to include the respective Module in an old-fashioned way?:

    include ActionDispatch::Routing::RouteSet


    If a NameError is raised telling you that ActionDispatch is unknown you might have to require 'action_dispatch'.

    ReplyDelete
  3. Maybe a stupid question, but is the fact that the class name and the file name don't match possibly a problem (IphoneHelperTest vs. iphone_test_helper.rb)? Sometimes that leads to classes not being loaded.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex