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.
On Tue, Oct 28, 2008 at 6: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.
Pat Maddox 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
aslak hellesoy wrote:
I recommend running against a production-LIKE environment. In Rails
you can create a production_test environment that you make as close to
your production environment as possible, for example by running
against a production_test database that contains a dump of your
One thing that bothers me about a 'staging' or 'production_test' environment
is simply the value of Rails.env. That should really == 'production', it
seems to me, but that's not always practical.
///ark
___
rspec-users mailing list
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,
On Oct 28, 2008, at 5:08 pm, Pat Maddox 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
On Tue, Oct 28, 2008 at 1: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.
I
On Wed, Oct 29, 2008 at 4:04 PM, DyingToLearn [EMAIL PROTECTED] wrote:
What about the idea of running it on machines that are as close to
production as possible? So if my production machine is a SliceHost VPS
with 256MB RAM, Nginx, and 3 Mongrels, then I should be running these
tests on a
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
10 matches
Mail list logo
