On Wed, Feb 18, 2009 at 3:15 PM, Stephen Eley <sfe...@gmail.com> wrote: > On Wed, Feb 18, 2009 at 3:02 PM, Ben Mabey <b...@benmabey.com> wrote: >> >> One option is to use ARMailer[1] to queue your mail. As long as your >> selenium process and test process are using the same DB without transactions >> getting in the way then ARMailer should work fine for what you want to do. > > Is changing production infrastructure solely for the sake of making > tests work a recommended practice? To me it feels a bit backwards.
I'm not commenting on this particular situation, but if I want to use some library, but I can't figure out how to write tests for my code that uses it, then I don't use it. Basically, if I have to change something to make it testable, I do. Pat _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users