similar to: Bug with assert_select and javascript?

I have the following html <p><b>text</b>value</p> I can use assert_select "p>b", "text" to check the text portion, and assert_select "p", "value" to check that the value appears in a <p>. I cannot work out how to check that the two are in the same <p>. I have used assert_select for much more complex tasks but my mind

Hi guys, I tried reading up the RSPEC Book (Dec 2010) and googled a bit but I could not find anything. I''m using Rspec2. Example: spec/factories/categories.rb ====================== FactoryGirl.define do factory :category_intakes, :class => ''category'' do name ''intakes and filters'' description ''airfilters and

On 30 August 2010 15:47, Marnen Laibow-Koser <lists-fsXkhYbjdPsEEoCn2XhGlw@public.gmane.org> wrote: > Colin Law wrote: >> I have the following html >> <p><b>text</b>value</p> >> I can use >> assert_select "p>b", "text" >> to check the text portion, and >> assert_select "p", "value"

Hi everyone, I am a bit confused with xhr? and respond_to. I have the folloing code in my view to update the ''emails'' ID link_to_remote(image_tag("refresh"), :update => "emails", :url => { :action => "list_emails" }) in the controller side i have somthing like : [..] respond_to do |type| type.html { render :action

Hello, One of my functional tests looks like this: def test_presence_of_free_text profile = Profile.find :first post :edit, {:id => profile.id} assert_select "textarea", :name => "record[free_text_ec]" end The test results in a failure, because the element cannot be found. I''m pretty sure the element should be there, and I''ve tried

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,

Hi all This is my first post here. I ave been using Rails for a couple of months, and am starting to put together a test suite. But I''m having a problem with assert_select in my functional tests. According to the documentation, it should be fine with two arguments - a CSS selector and a string to test it against. But no matter what I do I keep getting the exception: wrong number of

Hi everybody. Assert_no_tag will be deprecated soon. How can i use assert_select for checking not existed tag? Thanks. Bye. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To

I''d like to do an assert_select where only ONE of the matching elements needs to match the :text. It seems counterintuitive to me to require them *all* to match, which precludes me from testing the existence of a particular tag (h1) with some particular text if other instances of the same tag exist. I know that I can narrow down the field by using more detailed selectors, but it sure

I''m having trouble getting the specs to run for a plugin where I want to fix a bug. (I''ve actually already found and fixed the bug, but I don''t want to submit a fix without a test!) When I started the specs weren''t running, but it may be that I''m using Rails 2.3.3 and the plugin has been tested on 2.1 and earlier. I went through writing a spec for a

If I have a file in view /test called index.js.erb and in it a simple alert("hello") shouldn''t that run when I go to /test/index? It doesn''t. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it,

I''ve been battling with assert_select in my integration tests for several evenings now. I''m testing a multi-step form, and after submitting the first step, my assert_selects fail on the attempts to find the form on the next page. However if I print out the response object, it has the exact text of what I''m trying to match. Here is the complete integration test. The

Hey guys, I was having issues with some of the way assert_select worked, so I wrote an alternative to assert_select using hpricot. The major differences: * You get full support for CSS3 and limited XPath * It uses hpricot, which is fast; plus you get improvements to hpricot for free in assert_elements as long as you update the gem. * Blocks work a bit differently (assert_elements tests whether

Railsers: I''m playing with the Beast, and this test fails: def test_should_show_topic_as_rss get :show, :forum_id => forums(:rails).id, :id => topics(:pdi).id, :format => ''rss'' assert_response :success assert_select ''channel'' end It emits "ignoring attempt to close channel with link". So why are

Rubyists: Consider the following monstrosity, coded using assert_select: assert_select "div#logo_box img[src=/0000/0001/logo.gif][alt=My Company]" Now, behold it rewritten to use assert_xhtml: assert_xhtml do div.logo_box! do img :src => /logo.gif$/, :alt => ''My Company'' end end That sample contains more Ruby; it''s not just

just for the record, i tried searching the archives on this one but would get an application error when i tried entering |= in the search field. assert_select ''[foo|=bar]'' behaviour does not seem to jive with the css specs: http://www.w3.org/TR/CSS21/selector.html#q1 http://www.w3.org/TR/css3-selectors/#selectors is there some reason i don''t know about for this or is

Have you ever wanted to test your API output without those pesky assert_select error messages? Well now you can! http://dev.rubyonrails.org/ticket/8173 The patch has been sitting there quietly with no comment for a couple months now. I think it should be pretty easy to apply. It won''t affect standard HTML output or even XHTML given IE''s inability understand the standard

hi guys, I am testing a new optional funtionality in my site with IE 8 after success with Firefox 3.6.3, chrome and safari. The new functionality basically sees a "sub category" drop down list get generated in my form as soon as a "Category" value is selected from the "Category" drop down list. I have been using the standard rails api such as observe_field, and

Hello everyone: I am kind of puzzled in writing spec on view partials. I can not find much information about the "should have_tag" syntax in Rspec. Can rspec test a particular attribute of a tag (e.g. input tag)? Let me put an example here: #../view/group/_index <div id="test"> <input type="button" value="update" onclick="update()"

Hi, we''re exporting a lot of html code within xml, our current method works but it''s very messy - far from perfect, is there a better way to do this. an example of our controller code is html = html + "&lt;img src=&quot;/icon/icon_email.gif&quot;