#4628 Use assert_respond_to because it has better error messaging - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

This project is archived and is in readonly mode.

#4628 ✓resolved

Use assert_respond_to because it has better error messaging

Reported by Neeraj Singh | May 17th, 2010 @ 07:25 PM

If an assertion using assert_respond_to fails then it produces nice error message like this

  ActionMailer::Base
  of type Class
  expected to respond_to? :custom_settings.

compared to error message that is generated by assert.

false is not true.

Neeraj Singh May 17th, 2010 @ 07:43 PM
- Tag changed from “actionpack, rails3” to “actionpack, patch, rails3”
Attached is a patch.
- 4628_fix_against_rails3_edge.diff 2.9 KB
Repository May 18th, 2010 @ 02:19 AM
- State changed from “new” to “resolved”
(from [73f0e1a8423d53370f272841ce29747434de4d9a]) Use assert_respond_to because it has better error messaging

[#4628 state:resolved]

Signed-off-by: José Valim jose.valim@gmail.com
http://github.com/rails/rails/commit/73f0e1a8423d53370f272841ce2974...

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>