Rick Denatale wrote: > On Mon, Jun 9, 2008 at 8:18 AM, Nicholas Wieland > <[EMAIL PROTECTED]> > wrote: > >>> >> >> I haven't been clear enough, my point is not to fake the file upload >> (there's also fixture_file_upload for that) but to fake the receiver, making >> it dumb enough to avoid performing every operation on the file (in my case, >> uploading to s3). >> > > I'm pretty sure the problem is that by the time you stub has_attached > file, > which is a class method run when the class is loaded, it's too late. > Based > on a quick look at the paperclip project site, it looks like what you > want > to stub is the save_attached_files method on the model INSTANCE, which > the > has_attached_file registers as an after_save callback. > -- > Rick DeNatale > > My blog on Ruby > http://talklikeaduck.denhaven2.com/
Rick, I'm interested finding out how to do this, too (Rspec newbie and really terrible with mocking & stubbing). Are you suggesting we do something like this (?); Paperclip.saved_attached_file.stub!(:avatar).and_return(true) It's nice to be able to spec the app actually working with S3 but, my specs are taking over 3 minutes now and commenting out all the S3 involved specs kinda makes me nervous! -- Posted via http://www.ruby-forum.com/. _______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
