Not sure if I'm understanding right, but no, I can make the method public -- I just got used to methods, that aren't (or don't need to be) called by anything but its owner, being private.
If I make it public it solves my question somewhat :) Thanks, Ramon Tayag On Wed, Nov 19, 2008 at 9:52 PM, David Chelimsky <[EMAIL PROTECTED]> wrote: > On Wed, Nov 19, 2008 at 7:17 AM, Ramon Tayag <[EMAIL PROTECTED]> wrote: >> I was reading some old posts on how we shouldn't test private methods, >> but there seemed to be an exception for states. >> >> When my model enters a state, a method is executed. (:on => Proc ...) >> I just want to test this method. I couldn't find much material on it. >> How can I go about this? > > While there are always exceptions to guidelines, I've never seen a > general exception to "don't test privates" for states. > > Are you averse to just going at this from the public API? > >> >> Thanks, >> Ramon Tayag >> _______________________________________________ >> rspec-users mailing list >> rspec-users@rubyforge.org >> http://rubyforge.org/mailman/listinfo/rspec-users >> > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users > _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users