David Kahn wrote in post #978011: > On Thu, Jan 27, 2011 at 4:01 PM, William Fisk > <william.f...@gmail.com>wrote: > >> Ah, thanks, yes that will probably be the reason. > > > Right... send comes in real handy in testing private methods, use it all > the > time
Then you've got bigger problems. You shouldn't be testing your private methods; that's poking too deeply into an object's implementation. You should only ever test things that can be called from outside an object. If a private method is an intermediate value in a computation, just test the end result. If a private method really needs to be tested separately, then it's telling you that it wants to be public. Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org Sent from my iPhone -- 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 post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
