I agree. I have seen way too many times selenium tests are OK but bugs appear in production. Not only should we run selenium tests against production environment, but also they should be run on a production like environment, such as, same OS, same setting (behind Apache, or whatever HTTP servers, etc.)
On Tue, Oct 28, 2008 at 12:08 PM, Pat Maddox <[EMAIL PROTECTED]> wrote: > When you do end-to-end acceptance testing with Selenium, I think it > should be run against a production environment. Not THE production > environment, mind you, but simply a new Rails app running with > RAILS_ENV=production. Also, transactional fixtures should be turned > off. This is so that the app runs as closely as possible to how it does > from a regular user's perspective. Models and pages get cached, > transactions commit and rollback as they're defined, etc. What do you > think? Am I off base here? > > Pat > _______________________________________________ > rspec-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/rspec-users >
_______________________________________________ rspec-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/rspec-users
