I was wary of taking an approach like that, as it feels a little like test code bleeding into production code, but the sheer number of problems I'm having trying another way tells me that I'm very inadvisedly swimming against the stream, here. So I think I'll rethink my strategy & try something more like this -- thanks! Doug.
On 17 July 2010 17:58, Steve Klabnik <st...@steveklabnik.com> wrote: > One of the things that you learn after testing for a while is "what to > test." You don't need to test Paperclip's ability to put files to S3; that's > what Paperclip's internal tests are for. So what I do is this: > > http://gist.github.com/479647 > > When I'm developing locally or testing, I just write files to my local > machine. On production, they go to S3. > > _______________________________________________ > 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
