similar to: second assert_tag failling in rails integration test

Good morning (Pacific Time). I have a controller action that, as a side-effect, sends an email to an administrator. I want it to do something like this: specify "when someone successfully signs up, an email should be sent to the administrator with the person''s contact page" do post :signup, {...lots o'' params} response should_be success #

I''m using the functional test for a method like this: def test_create post :create, :phase => ''copynew'', :id => 1 assert_response :success assert_template ''create'' assert_tag :content => ''New Item'' assert_not_nil @item end This posts a request to the create method in the controller. Is there any way to look

I''ve run into another functional testing issue. Odds are I''m taking the wrong approach, so I''m back to this list again in the hopes of finding the true path. with assert_tag, I''d like to check the values of various table cells and ensure that the proper values are placed in the appropriate places. I written some tests that make good sense to me, and in

I''m getting strange errors attempting to test an rxml view with assert_tag. I can see that what the view is producing is correct but I get an error like "ignoring attempt to close foo with bar" (where bar is a tag which is meant to be nested in foo). Is asssert_tag meant for xml, or just html? Cheers, Robert. -- Posted via http://www.ruby-forum.com/.

Hi all, I can't seem to make assert_select work for the more complex cases for me. Here's a sample: # View <%= link_to_remote 'Add new', :url => new_phone_url, :submit => 'phones_head' %> # Generated code: <a href="#" onclick="new Ajax.Request('http://test.host/admin/parties/phone/new', {asynchronous:true, evalScripts:true,

Howdy all Apologies to the folks subscribed to the globalize list for dual posting this message... I''ve got a project running globalize and rails 1.1.4, and I''ve only recently adopted a strong love for testing. Now my models are 100% tested (I must note that I do not make use of any translations in the database yet), and I''ve now started with functional tests before

Hi All, I have a seemingly simple problem - but can''t figure out the problem. I have a simple functional test like so: def test_should_show_search_dropdown get :index assert_response :success assert_template :search end Inspite of having search.rhtml in /app/views/layout, it fails with an error: 1) Error: test_should_show_search_dropdown(SearchControllerTest):

Hi list I''ve got a bit of a philosophical question. After just having discovered Selenium /Selenium IDE and the rails selenium plugin I''ve realized that it''s a whole lot easier to do functinoal testing than writing the traditional rails functional tests. However it implies that the development database consists of standardized test data (e.g the test & dev

Just playing around with converting an apps to the new REST goodness in edge rails, and I''m trying to work out how to convert/write the functional tests. Is the recommended way to explicitly use the actions (e.g. get :show, :id => ...; post :create,..., etc) and test the routes separately, or duplicate the request, in which case how is that done get "/", :id => 5

Help! I have a new/create process that works fine in the actual app. But when I test I always get a failure in the test_create section. Here''s some controller code: def new end def create begin @borrower = Borrower.new(params[:borrower]) if @borrower.save flash[:notice] = ''Borrower '' + @borrower.FirstName + '' '' +

Hello! I have certain methods in my Application Controller, that I need to access. Namely ApplicationController#logged_in_user The problem is, that when I try to access it, I get: NoMethodError: protected method `logged_in_user'' called for #<AdminController> Any ideas how I can circumvent that? Or are functional tests really not suited for any kind of logins and session work?

Hi there, So I have an odd error at the moment that only occurs when I run tests via rake. It''s happening with two tests now. Under a simple ruby run, the tests are fine, e.g.: D:\User\Code\ruby\prometheus>ruby test\functional\story_comments_controller_test .rb Loaded suite test/functional/story_comments_controller_test Started ......... Finished in 2.37 seconds. 9 tests, 65

Hi everyone, In an integration test I have assert_tag :content => /Quantity/ and this always fails, even though Quantity does exist in the html. Similarly, I have assert_no_tag :content => /Quantity/ , and this fails even when Quantity *doesn''t* exist in the html. Am I missing something here? Thanks Daniel

In a functional test, I want to call an action in another controller (a login) before testing things in the current controller. As far as I can tell from the extremely sparse documentation and the AWDR book, this seems to be impossible. The post() functions takes an action argument only, and that''s that. Surely I must be misunderstanding things? -- Calle Dybedahl

The test: test "should get new" do get :new, :room_id => @room.name assert_template(:ne) end the template new does not exists but the test does not get failure. Why? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

(I posted this yesterday but within 20 minutes my thread was hijacked so I''m not sure anyone really saw this.) I''ve been working my way through the Agile book and just completed the depot sample application. I learned quite a bit along the way. On page 171 we are led through the creation of a test (that fails) for new code. The new code (a search function) is left as an

I have a test method (below). def test_save_failed post( :edit, :record => StatusChanger.invalid_data_hash) assert_response :success assert_template ''edit'' assert assigns(:record) assert_equal false, assigns(:record).valid? end This particular method is part of a larger set of functional tests. If I run, $ ruby controller_test.rb -n

Anyone? -------- Original Message -------- Subject: Functional test problem Date: Wed, 14 Jun 2006 19:49:03 +0100 From: Chris T <ctmailinglists@gmail.com> Reply-To: ctmailinglists@gmail.com To: rails@lists.rubyonrails.org Embarrassingly late (apps already well advanced), have decided top get to grips with testing and am having a week hopefully covering everything I''ve

I added this test towards the end of the included file_column_helper_test.rb that shipped with the file_column plugin: def test_url_for_file_column_different_root_path Entry.file_column :image, :root_path => File.join(RAILS_ROOT, "public/files") e = Entry.new(:image => upload(f("skanthak.png"))) assert_match %r{/public/files/entry/image},

I have a login page that redirects to itself if the login is incorrect. The browser does: get login post login, with wrong username and password redirect back to login When the post action redirects back to login it sets a flash telling the user it failed. So far so good. The problem is that if I get another page after that, the flash is still there. It only disapears on the second.