search for: assertionfailederror

I''m writing a method_missing handler to "automagically" create assertions from predicate functions. So, for example, one use might be: assert_not_include ''joes@shmoe.com'', response.to -or- assert_include ''info@mydomain.com'', response.from The code is working properly, but when I trigger an assert, the backtrace shows something like:

...rders'', :action => ''update'', :company_id => "32", :id => ''1'' }).should == "/companies/32/purchase_orders/1" Which results in this failure Test::Unit::AssertionFailedError in ''PurchaseOrdersController route generation routes #update to /companies/32/purchase_orders/1'' The recognized options <{"action"=>"show", "id"=>"1", "controller"=>"vendor_purchase_orders", "company_i...

I wanted to use ARTS to add RJS in a behaviour driven way to my application, but I''m having some trouble asserting a replace_html with a partial. I''ve created a pastie (http://pastie.caboo.se/60694) which contains the RJS I want to spec, the spec which I already wrote and its failure message. I''m currently using RSpec-0.9.2

...if i am using assert_routing method I am getting below error Failure/Error: assert_routing({:path => "admin/categories/2"}, {:controller => ''admin'', :action => ''categories'', :sub_category => ''2''}) Test::Unit::AssertionFailedError: found extras <{:sub_category=>"2"}>, not <{}> Why assert_routing method is failing for second route? And also let me know I which scenarios should I use assert_routing, assert_generates and assert_recognizes?

Hi, We have a project with a db table ''test'' and a corresponding model Test. When we run rake to invoke our tests, rake fails with the following error: /usr/lib/ruby/1.8/test/unit/assertionfailederror.rb:5: Test is not a module (TypeError) We believe this is caused by some namespace conflict between our model named Test and rake''s own internals. If we rename our Test class, this problem disappears; however, Test really is the right name in this circumstance. Can anyone suggest a p...

...selenium.click "id=loginCloseButton" @selenium.click "css=#lnkLogin > span" @selenium.click "//button[@id='''']" begin assert @selenium.is_text_present("* Please provide your email address") rescue Test::Unit::AssertionFailedError @verification_errors << $! end I am getting following error while running the code: undefined method `assert'' for #<Object:0x298f9e8> (NoMethodError) Please help me to resolve this issue or tell me any other commands for that. Thanks in advance. Attachments:...

...39;', :action => ''list'' end end And the failing test and result - def test_new_using_get get ''new'' assert_response :redirect assert_redirected_to :controller => ''trees'', :action => ''list'' end Test::Unit::AssertionFailedError: response is not a redirection to all of the options supplied (redirection is <{:action=>"list", :controller=>"trees"}>), difference: <{}> I''m sure I''m missing something obvious but I haven''t managed to track it down and Googling...

...text.empty? assert_block(build_message(message, "<?> not found in JavaScript dialog.", pattern)) do window_text.match(pattern) end else raise Test::Unit:: AssertionFailedError.new( build_message(message, "No JavaScript window found.")) end ensure pipe.close if pipe && !pipe.closed? end end end end # test - will close and print the text of an opened javascript d...

...tive_support/testing/setup_and_teardown.rb:59:in `__send__'' ./test/../lib/../../actionpack/lib/../../activesupport/lib/active_support/testing/setup_and_teardown.rb:59:in `run'' Name: test_assert_emails_too_few_sent(TestHelperMailerTest) Type: Failure Message: <Test::Unit::AssertionFailedError> exception expected but was Class: <ActionView::TemplateFinder::InvalidViewPath> Message: <"Unprocessed view path found in [\"./test/fixtures\"]"> ---Backtrace--- ./test/../lib/../../actionpack/lib/action_view/template_finder.rb:156:in `check_view_paths''...