Re: [rspec-users] How are people speccing and cuke-ing Paperclip (with S3)?
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
Re: [rspec-users] Future of RSpec Integration Testing
"Integration testing" is also known as "full-stack testing." Basically, you're not testing isolated parts of the system, but the system as a whole. Cucumber is integration testing. rspec with 'integrate_views' is integration testing. ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
[rspec-users] Spec-ing delayed_jobs in the future
I've been looking into rspec-ing delayed_jobs lately, and I found a few resources on testing jobs that execute right away. But I couldn't find any that delt with testing a job that is delayed a week in the future, for example. Does anyone have any good resources on this? I'd appreciate it. Thanks, Steve ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
